maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brett Porter (JIRA)" <>
Subject [jira] Closed: (MRELEASE-494) Should fail during release:prepare if scm:url doesn't match working copy
Date Mon, 27 Sep 2010 21:31:32 GMT


Brett Porter closed MRELEASE-494.

    Resolution: Duplicate
      Assignee: Brett Porter

> Should fail during release:prepare if scm:url doesn't match working copy
> ------------------------------------------------------------------------
>                 Key: MRELEASE-494
>                 URL:
>             Project: Maven 2.x Release Plugin
>          Issue Type: Bug
>          Components: prepare
>    Affects Versions: 2.0-beta-9
>         Environment: Subversion SCM; working in a branch
>            Reporter: David M. Lee
>            Assignee: Brett Porter
> The release plugin should check scm:url against the output of {{svn info}}.  If they
don't match, it should fail with an error.
> We had a situation where the pom file in a branch was screwed up during a merge, such
that scm:url was incorrect.  In our case, it pointed to the trunk instead of the branch.
> This caused release:prepare to silently do the wrong thing.  It would still do the normal
edit/commit in the working copy of the branch, but then it would do the copy using the scm:url.
 In our case, this meant that the tag was copied from the trunk instead of the branch.
> In fact, release:perform also completed successfully; our only indication that there
was a problem was the version number of the released artifacts.
> We cannot set remotetagging=false due to the Subversion bug trying to copy with svn >

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message