Creating a release version already released corrupts the source pom files if the tag name is already in SCM.

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.