[
https://jira.codehaus.org/browse/MRELEASE-749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=294089#comment-294089
]
Bindul Bhowmik edited comment on MRELEASE-749 at 3/14/12 6:10 AM:
------------------------------------------------------------------
I realize the initial description was not very clear. Here is a simple use case:
A project with a standard subversion structure (trunk, branches, tags) has a
tag project-1.1 (tags/project-1.2). If there is a need to create a bug fix
release (1.2.1), a maintenance branch is created (branches/project-1.2.x) and
changes made in the branch. Now, you try and run the release plugin
(release:prepare) from the code checked out from the branch to create release
1.2.1. The release:prepare stage creates the proper tag in SVN
(tags/project-1.2.1), but the content in the tag is identical to
tags/project-1.2 rather than branches/project-1.2.x (with of course the version
changes from 1.2.1-SNAPSHOT to 1.2.1).
release:prepare run on code checked out from trunk works just fine.
Not sure if it is relevant, but here is some additional information:
- It is a multi-module maven project with a child module
- Subversion client: Subversion command-line client, version
1.6.17-SlikSvn-tag-1.6.17@1130898-X64
- Subversion server: Subversion version 1.6.1 (r37116)
- The branch above was created using Eclipse Subversive plugin ver.
0.7.9.I20110819-1700 (using SVNKit connector 1.3.5 r7406 (SVN 1.6.15
compatible))
was (Author: bindul):
I realize the initial description was not very clear. Here is a simple use
case:
A project with a standard subversion structure (trunk, branches, tags) has a
tag project-1.1 (tags/project-1.2). If there is a need to create a bug fix
release (1.2.1), a maintenance branch is created (branches/project-1.2.x) and
changes made in the branch. Now, you try and run the release plugin
(release:prepare) from the code checked out from the branch to create release
1.2.1. The release:prepare stage creates the proper tag in SVN
(tags/project-1.2.1), but the content in the tag is identical to
tags/project-1.2 rather than branches/project-1.2.x (with of course the version
changes from 1.2.1-SNAPSHOT to 1.2.1).
release:prepare run on code checked out from trunk works just fine.
Not sure if it is relevant, but here is some additional information:
- It is a multi-module maven project with a child module
- Subversion client: Subversion command-line client, version
1.6.17-SlikSvn-tag-1.6.17@1130898-X64
- Subversion server: Subversion version 1.6.1 (r37116)
> release:prepare copies contents of source of Subversion branch into release
> tag
> -------------------------------------------------------------------------------
>
> Key: MRELEASE-749
> URL: https://jira.codehaus.org/browse/MRELEASE-749
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.2.2
> Environment: Windows 7; Silk Subversion 1.6x client; SVN 1.6x
> Reporter: Bindul Bhowmik
>
> When releasing from a branch, release:prepare copies the content of the
> source of the branch into the release tag rather than the content of the
> branch
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
