Hi, I'd like to change the way the aspectj plugin works. Here's what I'd like to implement:
- make it a pre-goal of jar:jar - verify if there are aspects present in the source tree - if there are, weave the aspects on the *bytecode* (classes compiled by the java plugin) - the generated jar of the jar plugin will then contain the aspects This way, building an aspected project will be seamless. Of course we could have a property to turn off automatic aspecting if we want. Would that be ok? Note: The only fear I have is when Maven users using aspects also define a pre-goal on jar:jar. Would the aspect pre-goal be run before or after the user one? I think the user one should run before the aspect one. But is that what is going to happen? Thanks -Vincent --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
