Re: Maven-sar plugin changes
Mauro Talevi <[email protected]>
| Newsgroups | gmane.comp.java.jcontainer.interest |
|---|---|
| Message-ID | <[email protected]> |
peter-4lf8KW9E9MLMqX/[email protected] wrote: > > Maybe but many other plugins have that identical behaviour and IIRC in the > future you will be required to explicitly define which plugins are run. > > Even if it is run it has zero effect unless the user explicitly sets the > correct property. it was more of a logical issue rather than practical ;-) > The problem is that people who want generate a jar still have to either have > a custom maven.xml or pass in two goals on cli > given that the need to maven a single goal seems to be predominant, I'll leave it as is (after removal sar:init). sar:metagenerate is executed everytime but only does the metageneration if maven.sar.metagenerate=true in the project wanting to use it. > Can you make sure that this has not effected the engine component which uses > the metagenerate task but never attains the sar:metagenerate goal. tested with engine and demos. cheers