[
https://issues.apache.org/jira/browse/MNG-6959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17155713#comment-17155713
]
Rupert Madden-Abbott commented on MNG-6959:
-------------------------------------------
Thanks very much for the advice [~rfscholte], that is really helpful. I agree
it does look like I am abusing the jar packaging life-cycle here. I will have a
rethink.
"Once a skip parameter is introduced it is very hard to remove it, hence you
still see it in too many places. In the past if was a simple way to hack around
certain situations, but by now it is time to do things correct. "
That sounds like the right approach. It might also help if these properties
were deprecated, or documented as being discouraged as the prevalence of the
"maven.x.skip" parameter made it look to me, incorrectly, that the lack of one
for the jar plugin was merely an oversight.
> Add "maven.jar.skip" property
> -----------------------------
>
> Key: MNG-6959
> URL: https://issues.apache.org/jira/browse/MNG-6959
> Project: Maven
> Issue Type: Improvement
> Reporter: Rupert Madden-Abbott
> Assignee: Robert Scholte
> Priority: Minor
>
> The following properties are available from various plugins:
> * maven.test.skip
> * maven.install.skip
> * maven.deploy.skip
> For consistency, please can we also have maven.jar.skip?
> There is a skipIfEmpty parameter but there is no way to set it via a property.
> This is helpful in keeping a standard CI build script across multiple
> projects e.g. running mvn install, and keeping build specific various in the
> pom.xml.
> Current workaround is to configure the jar plugin with a phase of none but
> this is less consistent with the method of skipping other default plugins.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)