Re: [ajdt-dev] Using AJDT to modify an RCP plugin post-compile

[Andrew Eisenberg <andrew@xxxxxxxxxxxx>]

>> 1. your woven classes must be included in the same OSGi bundle/eclipse
>> plugin as the original classes so that the OSGi classloading rules
>> will not be violated
>> 2. you must update the MANIFEST.MF files for these bundles/plugins
>> appropriately so that these woven classes are on the bundle's
>> classpath
>
> That's a shame, I had hoped to be able to drop in a plugin / bundle that would transform several other ones.
> I suppose this limitation also applies to load-time weaving?

Since this is an RCP app, you may be able to create a feature patch so
that you would just augment the existing bundles with new (woven)
classes.

But also, yes, using Equinox Weaving (a variant of load-time weaving
for OSGi) will get around this situation and you will be able to weave
into other bundles.

>
>> 3. I wouldn't recommend using AJDT for Eclipse 3.2 to build your RCP
>> app.  So much has changed and things are a lot easier to use with the
>> most recent releases.  And since you need to include the
>> org.aspectj.runtime jar in your RCP app, I'd recommend using the most
>> recent release (or a dev snapshot).
>
> For sure, but the application itself is already built and uses Eclipse 3.2, so I'm not sure we can change that.

You should be able to use a more recent aspectj in an older Eclipse.
Also, the Eclipse version used to build the app is independent from
the eclipse target version.
>
> _______________________________________________
> ajdt-dev mailing list
> ajdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/ajdt-dev
>