gord cody opened MRELEASE-852 and commented
I recently upgraded several projects from maven-2.0.9 to 3.0.5
all of our svn repos contain the standard trunk/tags/branches
I did the first maven3 release. when releasing from the trunk of project x everything looks correct within the content of the latest tag. All poms look ok. prepare and perform worked as expected.
We try to release from branch of project y in the same manner.
The branch was created manually from a tag. The poms versions were adjusted manually AND the scm tag was adjusted manually.
From the top folder where the branch is checked out i run
mvn release:prepare -Dmaven.test.skip=true
i interactively set the next version of the submodules and set the scm tag to "R_x.y.z".
The tagname created in svn is correct, "tags/R_x.y.z" but the content is from ALL of the branches currently in that svn repo instead of just the branch i am doing the release from!
from the parent pom.xml within the branch:
<developerConnection>scm:svn:https://xyz.com:8443/svn/myrepo/branches/B_1.5\
the poms in the branch all have 1.5.2-SNAPSHOT.
The output of release:prepare shows:
[INFO] Tagging release with the label R_1.5.2...
[INFO] Executing: cmd.exe /X /C "svn --non-interactive copy --file C:\Users\qa\AppData\Local\Temp\maven-scm-1783318747.commit --revision 5455 https://xyz.c
om:8443/svn/myrepo/branches https://xyz.com:8443/svn/myrepo/tags/R_1.5.2"
The line above is missing the branch name. it should be:
[INFO] Executing: cmd.exe /X /C "svn --non-interactive copy --file C:\Users\qa\AppData\Local\Temp\maven-scm-1783318747.commit --revision 5455 https://xyz.c
om:8443/svn/myrepo/branches/B_1.5 https://xyz.com:8443/svn/myrepo/tags/R_1.5.2"
Affects: 2.4.2
gord cody opened MRELEASE-852 and commented
I recently upgraded several projects from maven-2.0.9 to 3.0.5
all of our svn repos contain the standard trunk/tags/branches
I did the first maven3 release. when releasing from the trunk of project x everything looks correct within the content of the latest tag. All poms look ok. prepare and perform worked as expected.
We try to release from branch of project y in the same manner.
The branch was created manually from a tag. The poms versions were adjusted manually AND the scm tag was adjusted manually.
From the top folder where the branch is checked out i run
mvn release:prepare -Dmaven.test.skip=true
i interactively set the next version of the submodules and set the scm tag to "R_x.y.z".
The tagname created in svn is correct, "tags/R_x.y.z" but the content is from ALL of the branches currently in that svn repo instead of just the branch i am doing the release from!
from the parent pom.xml within the branch:
<developerConnection>scm:svn:https://xyz.com:8443/svn/myrepo/branches/B_1.5\
the poms in the branch all have 1.5.2-SNAPSHOT.
The output of release:prepare shows:
[INFO] Tagging release with the label R_1.5.2...
[INFO] Executing: cmd.exe /X /C "svn --non-interactive copy --file C:\Users\qa\AppData\Local\Temp\maven-scm-1783318747.commit --revision 5455 https://xyz.c
om:8443/svn/myrepo/branches https://xyz.com:8443/svn/myrepo/tags/R_1.5.2"
The line above is missing the branch name. it should be:
[INFO] Executing: cmd.exe /X /C "svn --non-interactive copy --file C:\Users\qa\AppData\Local\Temp\maven-scm-1783318747.commit --revision 5455 https://xyz.c
om:8443/svn/myrepo/branches/B_1.5 https://xyz.com:8443/svn/myrepo/tags/R_1.5.2"
Affects: 2.4.2