| AJ only working in top-level RCP/plug-in [message #67769] |
Thu, 16 November 2006 03:25  |
Eclipse User |
|
|
|
Originally posted by: mailto.mike-wendler.de
Hi there,
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?
project structure:
support (AJ)
- demo (AJ
- framework (AJ)
- ...
Thanks a lot in advance for any hint!
Cheerio, Mike
|
|
|
|
| Re: AJ only working in top-level RCP/plug-in [message #67809 is a reply to message #67790] |
Thu, 16 November 2006 07:22  |
| Eclipse User |
|
|
|
Originally posted by: mailto.mike-wendler.de
Hi Matt,
thanks a lot for your prompt reply! And for your excellent article which
put me on the track again. Now everything is working as I'd expect and
starts to make fun ;-)
(well, apart from the OutOfMemoryExceptions now and then ...)
Cheerio and have a nice day! Mike
|
|
|
| Re: AJ only working in top-level RCP/plug-in [message #595326 is a reply to message #67769] |
Thu, 16 November 2006 05:36 |
| Eclipse User |
|
|
|
Hi Mike,
By default aspects only apply to types within the same project. There
are mechanisms such as the "aspect path" setting which allow aspects
to be applied across projects. For more info, see the "Managing multiple
projects" section in this article:
http://www.eclipse.org/articles/Article-Introducing-AJDT/art icle.html
Regards,
Matt.
Mike Wendler wrote:
> Hi there,
>
> 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?
>
> project structure:
>
> support (AJ)
> - demo (AJ
> - framework (AJ)
> - ...
>
> Thanks a lot in advance for any hint! Cheerio, Mike
>
>
|
|
|
| Re: AJ only working in top-level RCP/plug-in [message #595338 is a reply to message #67790] |
Thu, 16 November 2006 07:22 |
| Eclipse User |
|
|
|
Originally posted by: mailto.mike-wendler.de
Hi Matt,
thanks a lot for your prompt reply! And for your excellent article which
put me on the track again. Now everything is working as I'd expect and
starts to make fun ;-)
(well, apart from the OutOfMemoryExceptions now and then ...)
Cheerio and have a nice day! Mike
|
|
|
Powered by
FUDForum. Page generated in 0.14545 seconds
Home