[
https://issues.apache.org/jira/browse/SCM-1013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17963979#comment-17963979
]
ASF GitHub Bot commented on SCM-1013:
-------------------------------------
jira-importer commented on issue #1238:
URL: https://github.com/apache/maven-scm/issues/1238#issuecomment-2964658973
**[Richard Eckart de
Castilho](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=rec)**
commented
No because the build setup is inherited from a parent pom and some project
inheriting from that POM may want to use these functionalities while others may
not. So I am putting the staging functionality into a marker-file-activated
profile so projects/specific modules can choose to use them. Then the
profile-activation axis is gone and another mechanism is needed to ensure that
the stuff is only executed in a release build.
> Add skip parameter to all goals
> -------------------------------
>
> Key: SCM-1013
> URL: https://issues.apache.org/jira/browse/SCM-1013
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: New Feature
> Components: maven-plugin
> Reporter: Richard Eckart de Castilho
> Priority: Major
>
> Currently, the only way to conditionally execute this plugin is by either
> putting it into a profile or by putting it into a conditionally included
> submodule. But profile-based activation may not be flexible enough and
> putting it into a conditionally included submodule is quite inconvenient.
> Most Maven goals have a "skip" parameter that can be used to control them. It
> would be good if the Maven SVM goals would follow that approach as well.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
