[
https://issues.apache.org/jira/browse/MDEPLOY-267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17048510#comment-17048510
]
Robert Scholte commented on MDEPLOY-267:
----------------------------------------
The profiles assume that the deployments are done on the local system (so they
can be activated). However, if they are pushed and the CI server is responsible
for pushing, you can still have the 2 branches battling for the deployment.
I would expect that one of the branches shouldn't be built at all and not just
disabling installing/deploying. One of the next pushes would be another
SNAPSHOT version, that's again the one to build.
> 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)
