Re: [aspectj-users] Issue with AJDT automatically adding aspect path to

[Jeffrey Sinclair <jeff@xxxxxxxxxxxxxx>]

Andrew,

Thanks for getting back to me.

I've added the bugzilla entry:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=273770

Please feel free to rename the request. I did not assign the request to
any particular release, in the meantime is there any workaround that you
are aware of (besides ensure the ivy dependencies don't overlap)? I'm
guessing there isn't one.

Regards,

Jeff

On Sun, 2009-04-26 at 19:13 -0700, Andrew Eisenberg wrote:
> Your suggestion is a possibility.  This is a general problem with
> using classpath containers (such as the one that ivy uses).  This
> problem also appears when using the PDE and wanting to add a
> particular to the aspect path of another plugin.
> 
> The difficulty with implementing this feature is that although AJDT
> creates the classpath and aspect path that is sent to the compiler,
> JDT is still performing correctness checks on it.  So, even if AJDT
> chooses not to send a particular classpath entry to the compiler
> (because it is a dupluicate from elsewhere), JDT will still complain
> that the classpath is invalid.  I need to find a way around this,
> though.
> 
> This has been a long standing problem and it should be addressed.  Can
> you please raise an enhancement request for this on bugzilla?
> 
> --a