A project team has a set of classes that need to be instrumented two different ways with AspectJ, one to work within a webapp and the second to work standalone.
The classes are kept inside the webapp module, so processing them during the build to produce the war works okay. What's the best way to instrument these same classes the _other_ way for the standalone jar? I've suggested establishing separate modules for the 'different' jars and possibly putting the shared code in a third module, but they say it's not possible, and I don't have enough experience with AspectJ to argue the point. I agree it would probably complicate building in the IDE. At the moment they're doing it with profiles, and executing Maven twice to produce the different artifacts. Any suggestions? -- Wendy --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
