[jira] [Commented] (MDEPLOY-267) add a parameter to not deploy non snapshots (-DdeployOnlySnaphots=true/false)

["Herve Boutemy (Jira)" <ji...@apache.org>]

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

Herve Boutemy commented on MDEPLOY-267:
---------------------------------------

disclaimer: I don't have yet an opinion if this should be done or not, just trying to understand and make the best possible proposal before deciding

I rewrote the issue description with Stephen's first comment as input, because this is the comment that made me understand what is tried to be achieved = avoid double release artifacts deploy (one from the release process, one from the CI)

one thing that lost me initially is the name of the parameter: {{-DdeployOnlySnaphots=true/false}}

given existing parameters, I would propose something like {{-DskipRelease=true/false}}

then this parameter could be set to "true" on normal builds, and overridden to "false" in the release profile: as described by Stephen, this would "ensure that all release deployments are made through the release plugin", which seems nice

> add a parameter to not deploy non snapshots (-DdeployOnlySnaphots=true/false)
> -----------------------------------------------------------------------------
>
>                 Key: MDEPLOY-267
>                 URL: https://issues.apache.org/jira/browse/MDEPLOY-267
>             Project: Maven Deploy Plugin
>          Issue Type: New Feature
>            Reporter: Olivier Lamy
>            Assignee: Olivier Lamy
>            Priority: Major
>             Fix For: 3.0.0
>
>
> maven-release-plugin creates a commit where the pom is not a SNAPSHOT version:  if CI system is configured to build on every commit and to deploy the artifacts on every build (with the intent in general to deploy updated SNAPSHOTs on every commit), the CI will deploy the non-SNAPSHOT that has already been deployed by the user who launched {{mvn release:perform}}, then it will generate an error (trying to override existing release artifact) and/or create new staging repository and/or override artifacts partially (if repository not configured to block overrides)
> we can add a new parameter {{-DdeployOnlySnaphots=true/false}}: it will be false per default for normal use, but can be configured to true in users' CI system.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)