|AJ only working in top-level RCP/plug-in [message #67769]
||Thu, 16 November 2006 08:25
Originally posted by: mailto.mike-wendler.de|
I'm having an RCP application consisting of several plug-ins (each in its
own eclipse project). On top of the top-level project a added a 'support'
RCP project which I converted to an AJ project. The application started
from this project runs just fine so project dependencies and compilation
is o.k. and anything.
The problem is that only those aspects work that crosscut classes in this
top-level 'support' project. Aspects defined on classes in the
'lower-level' projects do compile (i.e. the required classes are found
obviously) but the advice do not match. E.g. an aspect 'Test' shows the
warning 'advice in 'aj.Test' has not been applied [XLint:
adviceDidNotMatch]. The cross-references view confirms that.
The 'lower-level' projects (those I eventually want to test/enhance with
aspects) I have converted to AJ projects as well. Are there any other
preconditions for cross-cutting classes in other projects?
- demo (AJ
- framework (AJ)
Thanks a lot in advance for any hint!
Powered by FUDForum
. Page generated in 0.04923 seconds