[MRELEASE-1019] mvn release perform fails when the tag has the same name than a branch

**[Emmanuel Lécharny](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=elecharny)** opened **[MRELEASE-1019](https://issues.apache.org/jira/browse/MRELEASE-1019?redirect=false)** and commented

I tried to cut a release of Apache MINA 2.1.0 for a week, with no success. Actually, the release was fine, but the packages weren't pushed in the Nexus staging repo.

After investigation with Arnaud Héritier, it appeared that the tag we wanted to create collided with an existing branch, thus the release plugin was fetching the code from the branch, not from the tag, resulting in the target/checkout directory containing 2.1.1-SNAPSHOT versions of the code.

Renaming the branch to 2.1 solved the issue.

We do think that the release plugin should checkout the code from the created tag, and not from the branch.

---

1 votes, 4 watchers

Reproduce `mvn release:perform` with a tag and branch sharing the same name, then trace how the release plugin selects the checkout revision and inspect the resulting `target/checkout` contents. Done means the perform step checks out the created tag rather than the branch and the released code does not contain the branch's SNAPSHOT versions.

Written by the indexing model from the issue text.