maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arnaud HERITIER (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MRELEASE-1019) mvn release perform fails when the tag has the same name than a branch
Date Mon, 04 Mar 2019 13:15:00 GMT

    [ https://issues.apache.org/jira/browse/MRELEASE-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16783357#comment-16783357
] 

Arnaud HERITIER commented on MRELEASE-1019:
-------------------------------------------

[~elecharny] could you share you logs to show the issue to the team.

They'll better understand the clash between the 2.1.0 branch you have and the 2.1.0 tag you
wanted to create and thus why the checkout was getting the branch content in release:perform
instead of the tag

Thx

> 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)

Mime
View raw message