[
https://issues.apache.org/jira/browse/MSHADE-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17232742#comment-17232742
]
Andreas Rauchberger commented on MSHADE-251:
--------------------------------------------
I'm using profiles a lot, for controlling wether to execute a plugin in certain
circumstances or not.
e.g. sign the code for production but skip it for dev, ... and so on. or skip
shade/docker if we need to deliver a Main+shell-script (or a windows service)
the basic approach i'm following is to have a build-pipeline in maven
containing anything needed, then use profiles to disable certain plugin
executions if there is no current need.
what i do see as a massive overhead is declaring the same build steps in each
profile to just being able to skip the one currently not needed - this is a
guarantee for inconsistence the later refactoring will happen.
i east don't get the problem adding a skip-switch like 95% of maven-plugins
already do.
> Add skip parameter to shade goal
> --------------------------------
>
> Key: MSHADE-251
> URL: https://issues.apache.org/jira/browse/MSHADE-251
> Project: Maven Shade Plugin
> Issue Type: New Feature
> Reporter: Jonathan Haber
> Priority: Minor
>
> Most Maven plugins have a skip parameter but not the shade plugin. Our
> use-case is that we have multiple ways of packaging apps for deployment
> (using the shade plugin is one such way). We have these packaging plugins
> defined in our shared parent POM and projects can use Maven properties to
> control which ones to skip and which to execute.
> We've added this feature on our fork (which you can view
> [here|https://github.com/HubSpot/maven-plugins/compare/3fb23118d33d842e56a05cc94388d0b40f1bd7e3...811af68429b3728eaef1f8fc42a32bdb2571a8b1]).
> It's not much code and having a skip parameter can be a lifesaver when you
> need it, so I was hoping this feature could get added. Let me know what you
> think.
> Thanks,
> Jonathan
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
