When you want your aspects to apply across plugins, things become significantly more difficult because of the way that Eclipse manages its dependencies. When you do things like this, you can no longer use compile time weaving, but you must use a special form of load time weaving that leverages Equinox Aspects (load time weaving in an OSGi environment). This is how AJDT itself is built.
You can read a bit more about Equinox Aspects here: http://www.eclipse.org/equinox/incubator/aspects/ And feel free to ask any questions you need here. On Fri, Mar 18, 2011 at 5:11 AM, Davidosky <davide.arest...@gmail.com> wrote: > Hi all, > i've a problem exporting a PDE RCP plugin product that uses aspectj. > > Before refactoring this project, it had a local implementation for every > plugin of aspects used, and exporting the product was not a problem (I used > the build.properties file with those lines : > compilerAdapter=org.eclipse.ajdt.core.ant.AJDT_AjcCompilerAdapter > sourceFileExtensions=*.java, *.aj ) > > After adding a plugin that contains all the aspects previously were in every > plugin, the application runs fine from eclipse, but, when i export the > product, it gives an error when doing something that involves aspects > implemented. > > So, what can I do to solve this problem?! > > Davide > > -- > View this message in context: > http://aspectj.2085585.n4.nabble.com/AspectJ-PDE-export-problems-tp3387024p3387024.html > Sent from the AspectJ - users mailing list archive at Nabble.com. > _______________________________________________ > aspectj-users mailing list > aspectj-users@eclipse.org > https://dev.eclipse.org/mailman/listinfo/aspectj-users > _______________________________________________ aspectj-users mailing list aspectj-users@eclipse.org https://dev.eclipse.org/mailman/listinfo/aspectj-users
