Re: Maven-sar plugin changes
Mauro Talevi <[email protected]>
| Newsgroups | gmane.comp.java.jcontainer.interest |
|---|---|
| Message-ID | <[email protected]> |
Peter Donald wrote: > I have just made a change that may break some setups. Rather than sar:generate > attaining the jar:jar goal I added sar:generate as a postGoal to > java:compile. The reason was that I had a need for the metadata to be present > between java:compile and jar:jar. So hopefully that wont effect too many > people and if you are just using the plugin in standard fashion then > everything should continue to work as is. The problem with this approach is that whenever someone calls java:compile, even in projects that have nothing to do with metageneration of code, the sar:metagenerate will get invoked. I would prefer to keep sar plugin depend on jar but not viceversa. Would setting a preGoal on jar:jar to attain sar:metagenerate whenever necessary in a specific project (but not in the plugin) not do the same trick? BTW, I've changed the default metagenerate src to take the value from pom.build.sourceDirectory. Cheers