[
https://issues.apache.org/jira/browse/MDEPLOY-267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17048285#comment-17048285
]
Robert Scholte commented on MDEPLOY-267:
----------------------------------------
This is about a ratrace condition where 2 "branches" both try to deploy a
non-SNAPSHOT, because the maven-release-plugin first pushes the master/develop
branch, and ater that the tag. In such case you'd always want the tag to win.
I've hit a similar situation with jgitflow and managed to fix this in the
pipeline by saying: only build if it is the master branch (with jgitflow this
is where are all non-snapshots are merged too) or the project is a SNAPSHOT.
[~stephenc] what's your idea here?
> 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
>
>
> in case of maven-release-plugin it happen the pom contains non SNAPSHOT
> version and so CI system try to deploy the artifacts this can generate an
> error and/or create new staging repository
> we can add a new parameter -DdeployOnlySnaphots=true/false. For backward
> compat it will be false per default but users will be able to configure their
> CI system.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
