[
https://issues.apache.org/jira/browse/MSHADE-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17231423#comment-17231423
]
Delany commented on MSHADE-251:
-------------------------------
I don't know what world you're living in where people randomly add parameters
to command lines, my colleagues all have keyboard-phobia, they'd do anything to
use a shorter build command.
Imagine if we were making desk lamps without on/off switches. People must pull
it out of the wall? Ridiculous.
And as for profiles, thats exactly what I've done. Hundreds of profiles for
switching plugins and off. But of course I can't just turn on a profile by
default, because that would turn off the other profile that was turned off by
default, hence
{{<activation>}}
{{ <property>}}
{{ <name>!muaeixubuayol</name>}}
{{ </property>}}
{{ </activation>}}
And that's when I didn't just bind the plugin to a non-existent phase! Which
makes three ways that plugins are being toggled.
> 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)
