[MRELEASE-322] Unable to set the working directory for projects where the master pom isn't at the root of the project

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 2.0-beta-7
• Fix Version/s: 2.0
• Component/s: scm
• Flags: Patch
• Assignee: Maria Odea B. Ching
• Reporter: Christian Nelson
• Created: 04/Feb/08 16:50
• Updated: 05/Apr/15 14:54
• Resolved: 24/May/09 00:45

Description

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:

[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

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?

Issue Links

• duplicates: MRELEASE-261 release:prepare should support flat directory multi-module projects