You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Andreas Rauchberger (Jira)" <ji...@apache.org> on 2020/07/31 08:17:00 UTC

[jira] [Commented] (MSHADE-251) Add skip parameter to shade goal

    [ https://issues.apache.org/jira/browse/MSHADE-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17168510#comment-17168510 ] 

Andreas Rauchberger commented on MSHADE-251:
--------------------------------------------

i do see the <skip> parameter more or less as a default maven-plugin feature/&strategy.

it really makes things easier. we do use the parent-pom-approach a lot to generalise things.

we then use profiles (mainly setting properties there) to do things like "build-only", "build-and-docker", "build-release", ... controlling which plugins to execute.

i think this is a common approach, and prevents the user from knowing/providing all properties on command line.

> 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)