[
http://jira.codehaus.org/browse/MRELEASE-322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=129950#action_129950
]
Torben Giesselmann commented on MRELEASE-322:
---------------------------------------------
How about using the option {{-DcommitByProject=true}} ?
Does that change anything?
> Unable to set the working directory for projects where the master pom isn't
> at the root of the project
> ------------------------------------------------------------------------------------------------------
>
> Key: MRELEASE-322
> URL: http://jira.codehaus.org/browse/MRELEASE-322
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: scm
> Affects Versions: 2.0-beta-7
> Reporter: Christian Nelson
> Priority: Blocker
>
> Branches and Tags are created from the current working directory, which isn't
> always correct and there isn't a way to override the working directory.
> For example, we have the following directory structure:
> ${root}/master/pom.xml - The modules section include relative paths to
> modules a, b, and c.
> ${root}/module-a/pom.xml
> ${root}/module-b/pom.xml
> ${root}/module-c/pom.xml
> All subversion copies (via branch or prepare) originate from ${root}/master.
> As a result, they are incomplete; we really want to create copies from
> ${root} not ${root}/master. Here's the subversion command that I think is
> the problem:
> {noformat}
> [INFO] Working directory: C:\devsys\repos\trunk\master
> [INFO] Branching release with the label release-1.0...
> [INFO] Executing: svn --non-interactive copy --file
> C:\Users\cnelson\AppData\Local\Temp\maven-scm-1179760787.commit .
> http://hostname/svn/dev/branches/release-1.0
> {noformat}
> The period after the filename is what's indicating to subversion to create
> the copy from master instead of ${root}. Note: the working directory is
> derived from the basedir and I couldn't find a way to override the basedir.
> While not having the master pom at the root of the project may be a little
> uncommon, it doesn't seem unreasonable. Can we add a configuration option to
> handle these cases?
--
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
