[
https://issues.apache.org/jira/browse/MRELEASE-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16783379#comment-16783379
]
Emmanuel Lecharny commented on MRELEASE-1019:
---------------------------------------------
Here is a copy of the logs :
https://paste.apache.org/zqEL
> mvn release perform fails when the tag has the same name than a branch
> ----------------------------------------------------------------------
>
> Key: MRELEASE-1019
> URL: https://issues.apache.org/jira/browse/MRELEASE-1019
> Project: Maven Release Plugin
> Issue Type: Bug
> Reporter: Emmanuel Lecharny
> Priority: Major
>
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
