[
https://issues.apache.org/jira/browse/SCM-783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17964953#comment-17964953
]
Olivier Lamy commented on SCM-783:
----------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-scm#990|https://github.com/apache/maven-scm/issues/990].
> Support existence check for tags and branches
> ---------------------------------------------
>
> Key: SCM-783
> URL: https://issues.apache.org/jira/browse/SCM-783
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: New Feature
> Components: maven-scm-api
> Reporter: Robert Scholte
> Priority: Major
>
> The {{prepare}} goal of the maven-release-plugin does the following scm tasks:
> # commit the adjusted pom.xml with final versions and new
> (developer)connection
> # tag
> # commit the adjusted pom.xml for the next development cycle.
> If step 2 fails because the tag already exists, the pom is in a wrong status
> at the trunk. A next attempt to do the {{prepare}} will fail. To prevent this
> simple mistake is by checking the existence of the tag *before* step 1.
> The same should be done for branches.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
