You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Peter Grape (Jira)" <ji...@apache.org> on 2020/05/25 09:46:00 UTC

[jira] [Created] (MRELEASE-1047) Creating a release version already released corrupts the source pom files if the tag name is already in SCM.

Peter Grape created MRELEASE-1047:
-------------------------------------

             Summary: Creating a release version already released corrupts the source pom files if the tag name is already in SCM.
                 Key: MRELEASE-1047
                 URL: https://issues.apache.org/jira/browse/MRELEASE-1047
             Project: Maven Release Plugin
          Issue Type: Bug
          Components: perform
    Affects Versions: 3.0.0-M1, 2.5.3
            Reporter: Peter Grape


*Problem:*

If you create a release with the same version that has already been released, causes the release process to be halted due to a SCM Tag name conflict in Git and most likely other SCMs as well and the POM files will enter a invalid state since the released versions are checked in.

*Suggested solution:*

A verification step needs to be added to make sure the generated tag name is not already set. and stop the process there.

 



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