You might be able to achieve something using the mechanism for configuring compilation with aop.xml files (like you configure load time weaving). I mentioned it here a while back: http://dev.eclipse.org/mhonarc/lists/aspectj-dev/msg02602.html
For each project you could use an appropriate aop.xml to scope what you want to apply where. However, i don't know if that option plays nicely with maven. Andy On 7 February 2014 03:25, Sean Patrick Floyd <seanpfl...@googlemail.com>wrote: > Hi, > > I am currently moving aspects from a regular multi module maven project > with production code to a separate aspect library (different maven > artifact). > However, I need different modules of my production code to use different > subsets of the aspect library. > > Is there a possibility to limit the aspects I use from an external library > by package? > > e.g. > > parent > - project a > - project b > - project c > > where each of these projects is woven against lib "external" using the > packages > - external.common and external.a > - external.common and external.b > - external.common and external.c > respectively. > > Is this kind of setup possible with maven or ant or do I have to split my > aspect libraries into a multi module project also? > > Regards, Sean > _______________________________________________ > 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
