You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Robert Scholte (Jira)" <ji...@apache.org> on 2020/07/10 14:40:00 UTC
[jira] [Closed] (MNG-6959) Add "maven.jar.skip" property
[ https://issues.apache.org/jira/browse/MNG-6959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte closed MNG-6959.
-------------------------------
Assignee: Robert Scholte
Resolution: Won't Fix
The ultimate goal of every build is the creation of an artifact, so it doesn't make sense to skip the creating of a jar.
Any skip-argument is a workaround for a different problem, so you should create a ticket that would make the need of this skip obsolete.
> 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)