[
https://issues.apache.org/jira/browse/MNG-7691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17711838#comment-17711838
]
Delany commented on MNG-7691:
-----------------------------
https://issues.apache.org/jira/browse/MSHADE-251
Although I don't need this personally, I don't buy Robert's paternalistic
arguments against skip properties. The question should rather be: where has
anyone ever complained about the existence of a skip property? Adding a command
line switch and removing inadvertently added switches is trivial. If I'm so
concerned about the inefficiencies they introduce I'll refactor the poms as a
more permanent solution. Functionality first, efficiency later.
> Provide a generic way to skip Maven Goals for a specified plugin
> ----------------------------------------------------------------
>
> Key: MNG-7691
> URL: https://issues.apache.org/jira/browse/MNG-7691
> Project: Maven
> Issue Type: Improvement
> Components: Plugins and Lifecycle
> Reporter: Jimisola Laursen
> Priority: Major
>
> From ([Baeldung|https://www.baeldung.com/maven-disable-parent-pom-plugin]:
> "Many plugins feature a skip parameter. We can use the skip parameter to
> disable the plugin. Support for the skip parameter should be the first thing
> we check because it is the simplest solution and the most conventional.".
> I was thinking that there should be a generic way to skip maven plugin goals
> in the core of Maven, i.e. it should not have to be implemented in each
> plugin.
> Would something like this work?
> -Dmaven.skip.goals=groupID:artifactId:goal (is there a need to specify
> version?)
> E.g.
> -Dmaven.skip.goals=io.spring.javaformat:spring-javaformat-maven-plugin:apply
> -Dmaven.skip.goals=io.spring.javaformat:spring-javaformat-maven-plugin:apply+validate
> -Dmaven.skip.goals=io.spring.javaformat:spring-javaformat-maven-plugin:apply+validate,org.apache.maven.plugins:maven-enforcer-plugin:enforce
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
