[news.eclipse.technology.ajdt] Re: Binary cycles while exporting RCP pro

["Gaston M. Tonietti" <gaston.tonietti@xxxxxxxxxxxx>]

Ok. I tried to build the product using scripts from ajdt-pde-build plugin but it fails:
org.eclipse.ajdt.pde.build_2.0.1.200907072043/templates/headless-build/customTargets.xml:18: java.net.MalformedURLException: no protocol: 
${eclipseBaseURL}

But I think I understood what you said, so I created the build file in the project having the aspects, it generates a @dot folder with compiled aspects 
all right, and I built the product with the regular pdebuild script, thinking it will use the existing build.xml for the project with the aspects, but it 
wasn't this way :-( , this file was overridden by one without AspectJ support.

So I don't know what else to do.

My setup is, at least the part which matters now (I have more plug-in projects not related to this problem), a plug-in project with AspectJ capability 
called domain and an RCP product project called ui. Domain doesn't know anything about ui, while ui depends on domain (using Required-Bundles header) and 
uses Equinox Aspects for weaving at runtime. All this is working great in development.

So my problem is, that I get the domain plug-in jar with the MyAspect.aj file instead of the compiled one MyAspect.class, due that, weaving hook fails 
registering the aspect:
Cannot register non aspect: MyAspect , MyAspect

So what can I do in order to get an exported product with a domain plug-in jar containing proper aspect class?

Thanks a lot Andrew.
Gaston.

Andrew Eisenberg wrote:

> Hi Gaston,
> 
> I added a new attachment to the bug report that has the updated ajdt pde
> build plugin 3.5:
> https://bugs.eclipse.org/252641
> 
>> I have no checkbox for allowing cycles in "Export Eclipse Product with
>> AspectJ support". It is not an issue as now it does not fail due cycles
>> anymore. I saw it in "Export deployable plug-ins and fragments with
>> AspectJ support" but I need to export it as an eclipse product.
> Yes.  There is no check box for it.  The change I made turned on the flag
> by
> default (with no way of disabling it).  Bug 282391 is about adding UI
> support for this.
> 
>> I would like to clarify something, I don't know if it matters:
>> I don't have aspects in the product I'm exporting, but in another project
>> which the product depends on.
> 
> Yes, this may be an issue.  How do you have this set up?  Is the other
> project on the aspect path?  Is it another plugin project?
> 
> Right click on the manifest file for the plugin and select "Generate build
> file with AspectJ support".  Make sure that the project that you expect is
> on the aspect path.
> 
> --a