[
https://issues.apache.org/jira/browse/MJAR-269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MJAR-269.
-------------------------------
Assignee: Robert Scholte
Resolution: Won't Fix
This exposes a different problem: you want distrubution separated from
building. The wrong solution is skipping jar, in the end you always want a jar.
(just to make the issue clear: next request is probably skipping other plugins
such as compile or resources).
First thought I can thinks of:
- Some hook in Maven to make it possible to make the pipeline and Maven
interact with eachother.
- Improve Maven to make it easier to distribute, e.g. just calling
deploy:deploy. The downside of this is that Maven will doesn't control the
generated artifacts anymore, because the pipeline has changed it in the
meantime. This is a risk.
I do understand the request, but skipping is never the right solution, hence I
need to close this as won't fix.
> Add Skip Property to Skip Plugin Execution
> ------------------------------------------
>
> Key: MJAR-269
> URL: https://issues.apache.org/jira/browse/MJAR-269
> Project: Maven JAR Plugin
> Issue Type: New Feature
> Reporter: Brian Wyka
> Assignee: Robert Scholte
> Priority: Minor
> Labels: skip
> Original Estimate: 96h
> Time Spent: 10m
> Remaining Estimate: 95h 50m
>
> 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.3.4#803005)
