[
http://jira.codehaus.org/browse/MRELEASE-526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Damien Coraboeuf updated MRELEASE-526:
--------------------------------------
Attachment: export.zip
I've created a sample project that allowed me reproduce the problem.
The interesting thing is that I _cannot_ reproduce the problem if I run the
release:prepare command from my environment, but only when I run this build
from Hudson. So maybe it's linked somehow with Hudson.
Here is the actual build step that is called:
{noformat}
Executing Maven: -B -f /opt/hudson/jobs/MRelease-526/workspace/./pom.xml -B
clean install release:clean release:prepare -DautoVersionSubmodules=true
-DreleaseVersion=0.7.0 -DdevelopmentVersion=0.8.0-SNAPSHOT -Dtag=0.7.0
-DpreparationGoals=clean install
{noformat}
And here is the output about the tagging part:
{noformat}
[INFO] Checking in modified POMs...
[INFO] Executing: /bin/sh -c cd /opt/hudson/jobs/MRelease-526/workspace/. &&
svn --non-interactive commit --file /tmp/maven-scm-1832850485.commit --targets
/tmp/maven-scm-1057416757279716410-targets
[INFO] Working directory: /opt/hudson/jobs/MRelease-526/workspace/.
[INFO] Tagging release with the label 0.7.0...
[INFO] Executing: /bin/sh -c cd /opt/hudson/jobs/MRelease-526/workspace && svn
--non-interactive copy --file /tmp/maven-scm-1386345960.commit --revision 39
svn://192.168.37.24/maven/mrelease526
svn://192.168.37.24/maven/mrelease526/tags/0.7.0
[INFO] Working directory: /opt/hudson/jobs/MRelease-526/workspace
[INFO] Transforming 'Unnamed -
org.apache.maven:mrelease526:pom:0.7.0-SNAPSHOT'...
[INFO] Transforming 'Unnamed - org.apache.maven:moduleA:jar:0.7.0-SNAPSHOT'...
[INFO] Transforming 'Unnamed - org.apache.maven:moduleB:jar:0.7.0-SNAPSHOT'...
[INFO] Not removing release POMs
[INFO] Checking in modified POMs...
[INFO] Executing: /bin/sh -c cd /opt/hudson/jobs/MRelease-526/workspace/. &&
svn --non-interactive commit --file /tmp/maven-scm-1044767202.commit --targets
/tmp/maven-scm-4622755560941691278-targets
[INFO] Working directory: /opt/hudson/jobs/MRelease-526/workspace/.
[INFO] Release preparation complete.
{noformat}
> 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.0.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
