[
https://issues.apache.org/jira/browse/MJAR-269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17957332#comment-17957332
]
Matthias Bünger commented on MJAR-269:
--------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-jar-plugin#418|https://github.com/apache/maven-jar-plugin/issues/418].
> Add Skip Property to Skip Plugin Execution
> ------------------------------------------
>
> Key: MJAR-269
> URL: https://issues.apache.org/jira/browse/MJAR-269
> Project: Maven JAR Plugin (Moved to GitHub Issues)
> Issue Type: New Feature
> Reporter: Brian Wyka
> Assignee: Robert Scholte
> Priority: Minor
> Labels: skip
> Original Estimate: 96h
> Time Spent: 20m
> Remaining Estimate: 95h 40m
>
> Expose plugin configuration as well as a user property to allow the plugin
> execution to be skipped.
>
> There are occasions when we do not always want to run jar plugin.
>
> Example:
> In a build pipeline, we run different phases in different stages
>
> # Run install in isolation (we need jar here)
> # Run deploy in isolation (we don't need jar again - so need a way to skip)
>
> Currently there is only a hack to do this, by overriding the *default-jar*
> execution of the plugin and setting the phase to a user property, and then
> overriding that to a non-existent phase, to keep it from being attached to
> the maven lifecycle.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
