[
http://jira.codehaus.org/browse/MRELEASE-526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=214833#action_214833
]
Tim Collins commented on MRELEASE-526:
--------------------------------------
Same issue with mercurial, tagging fails because the working directory is one
level too high.
> release:prepare 2.0 goal tags at the wrong level, tagging project/ instead of
> project/trunk
> -------------------------------------------------------------------------------------------
>
> Key: MRELEASE-526
> URL: http://jira.codehaus.org/browse/MRELEASE-526
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.0
> Environment: Maven 2.2.1
> Reporter: Damien Coraboeuf
> Priority: Critical
> Fix For: 2.1
>
> Attachments: export.zip
>
>
> We have switched to the release plug-in 2.0 and are using the prepare goal as
> we did before using version 2.0-beta-9. Unfortunately, the tag which is now
> created is copied from the project level, and from the trunk. With version
> 2.0-beta-9, the tag was correctly copied from the trunk.
> With 2.0-beta-9:
> {noformat}
> /project
> |-- trunk/
> |-- pom.xml
> |-- src/
> |-- tags/
> |-- 4.0.1/ (<-- copied from trunk
> |-- pom.xml
> |-- src/
> {noformat}
> With 2.0:
> {noformat}
> /project
> |-- trunk/
> |-- pom.xml
> |-- src/
> |-- tags/
> |-- 4.0.1/ (<-- copied from trunk
> |-- trunk/
> |-- pom.xml
> |-- src/
> |-- tags/
> |-- branches/
> {noformat}
> Our _pom.xml_ SCM information is declared as follow:
> {noformat}
> <scm>
>
> <developerConnection>scm:svn:svn://host/path/project/trunk</developerConnection>
> </scm>
> {noformat}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
