[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [aspectj-users] weaving existing OSGi jars and exclusion of aspect classes
- From: Simone Gianni <simoneg@xxxxxxxxxx>
- Date: Fri, 12 Jun 2009 19:36:00 +0200
- Delivered-to: email@example.com
- User-agent: Thunderbird 126.96.36.199 (X11/20090102)
what you are talking about are "Aspect Libraries", that is a jar
containing aspect that is then applied to other classes. This can be
done by ajc and by the maven plugin. Let's call the jar containing the
aspects "library" and the jar containing classes to be woven "target".
Obviously target will have the library as a dependency. Then, the
library must be on the "aspect path" of ajc, to do this you can
configure the mojo as explained here
Another option is to use Equinox Aspects, which will apply your aspect
library bundle directly to the target bundle at runtime, using LTW
instead of compiling it during build time, making it very dynamic as it
should be in OSGi.
Hope this helps,
Captain Haddock wrote:
Ultimately trying to do the following:
- all aspect classes will be included in a single OSGi bundle
- existing OSGi bundles will be woven with aspects
Instead of including the aspect classes in the resulting bundle, I
would like to update the OSGi bundle's dependencies to include the
OSGi bundle containing the aspect classes.
So first thing is whether the aspectj-maven-plugin has ability to not
include the aspect classes? (I did not see a parameter to toggle this:
Second thing is the updating of the bundle dependencies .. anything
there that can help me? (or I will have to do via a bunch of manual
If these questions are better asked on another list then please advise.
aspectj-users mailing list
Simone Gianni CEO Semeru s.r.l. Apache Committer