I don't have a solution for you, but as you've not received an answer from anyone else I wanted to reply.
I have run into a similar situation with aop, but haven't really come up with a good solution. In my case, the aop weaving was just used for testing, so the dependency tree wasn't an issue for anyone else. /Anders On Fri, Nov 26, 2010 at 12:09, Akhilesh Singh <akhil...@zinniasystems.com>wrote: > Hi, > I am currently facing an issue in our project setup. The scenario is > something like this: > > 1) Project A -> Project B > -> Project C > > > 2) Project A-web -> Project A > Project D > > This works all fine as generated was for Project A-web conains all the > required jars. ( A, B, C,D) > > 3) Project A-woven -> Project A > Aspect-jar > > Now, we are creating a aspectj woven jar pf Project A using aspectj mojo. > The name of this module is Project A-woven. We want to include this jar in > the Project A-web instead of Project A. However, if I add Project A-woven > as > dependency and add Project A as exclusion in Project A-web( otherwise both > A > and A-woven will be present) , Project B and Proejct-C will also not be > included in the resulting war. Project A is a typical enterprise > application and has more than 20 jars as dependency which I don't want to > add again in Project A-web or Project A-woven. > > My idea is to add Project A-woven with Project-A as exclusion in Project > A-web while keeping the dependencies of A intact. Is this possible? > > Can anybody please help with suggestions on this? > > Regards, > *Akhilesh Singh* > *Chief Software Architect, * > *Zinnia Systems,* > *Mobile: +91 9742306306* > *http://www.zinniasystems.com* <http://www.zinniasystems.com/> >