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

**[Peter Grape](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=peter.grape)** opened **[MRELEASE-1047](https://issues.apache.org/jira/browse/MRELEASE-1047?redirect=false)** and commented

**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.

---

**Affects:** 2.5.3, 3.0.0-M1

1 votes, 1 watchers

No source files or tests are named. Trace the release process that generates and checks the SCM tag, then inspect existing release tests; done means an already-existing tag stops the process before source POM files are changed and leaves them valid.

Written by the indexing model from the issue text.