You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Christian Nelson (JIRA)" <ji...@codehaus.org> on 2008/02/04 23:51:57 UTC
[jira] Created: (MRELEASE-322) Unable to set the working directory
for projects where the master pom isn't at the root of the project
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
[jira] Updated: (MRELEASE-322) Unable to set the working directory
for projects where the master pom isn't at the root of the project
Posted by "Arnaud Heritier (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arnaud Heritier updated MRELEASE-322:
-------------------------------------
Patch Submitted: [Yes]
> 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
> Attachments: maven-release-manager-flat.patch, maven-release-plugin-flat.patch
>
>
> 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
[jira] Commented: (MRELEASE-322) Unable to set the working
directory for projects where the master pom isn't at the root of the
project
Posted by "Markus Klink (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_125785 ]
Markus Klink commented on MRELEASE-322:
---------------------------------------
I actually always had the impression that multiprojects encourage that a directory structure like the one outlined above is chosen. I was therefor very surprised to find out that maven release does not support it. How am I supposed to have my directory structure to be able to actually perform a release? For me this is a critical blocker, please fix.
Regards
Markus
> 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
[jira] Updated: (MRELEASE-322) Unable to set the working directory
for projects where the master pom isn't at the root of the project
Posted by "Nils Winkler (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nils Winkler updated MRELEASE-322:
----------------------------------
Attachment: maven-release-plugin-flat.patch
maven-release-manager-flat.patch
I am facing the same problem. Did some work on this, please have a look at the two attached patches. Here's what they do (in addition to bumping up the version to 1.1-SNAPSHOT, which probably isn't that great - but it works to tell them apart from the official version):
.h2 maven-release-plugin-flat.patch
* Moves the {{commitByProject}} attribute up to the {{AbstractReleaseMojo}} class. This way this attribute is available for both the prepare and the perform goals.
.h2 maven-release-manager-flat.patch
* If the {{commitByProject}} parameter is set, the tagging also goes through the list of projects in the reactor and commits each one of them.
* During the perform phase, the working directory is set to the directory containing the parent POM, i.e. {{master/target/checkout/master}}
You can run this like this:
{code}
master> mvn -DcommitByProject=true release:prepare
master> mvn -DcommitByProject=true release:perform
{code}
The tag patch currently expects a SCM management layout like this - tested with SVN:
{code}
/project
+trunk
+master
+module-a
+module-b
+tags
+foo-1.0
+master
+module-a
+module-b
{code}
I have implemented it like this since it reflects our current environment. To use a different layout, I would recommed playing around with the code in {{ScmTagPhase.java}}. Maybe another parameter could be added to specify the SCM layout to use.
Hope this helps some of you.
> 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
> Attachments: maven-release-manager-flat.patch, maven-release-plugin-flat.patch
>
>
> 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
[jira] Updated: (MRELEASE-322) Unable to set the working directory
for projects where the master pom isn't at the root of the project
Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maria Odea Ching updated MRELEASE-322:
--------------------------------------
Fix Version/s: 2.0-beta-10
> 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
> Assignee: Maria Odea Ching
> Priority: Blocker
> Fix For: 2.0-beta-10
>
> Attachments: maven-release-manager-flat.patch, maven-release-plugin-flat.patch
>
>
> 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
[jira] Issue Comment Edited: (MRELEASE-322) Unable to set the
working directory for projects where the master pom isn't at the root of
the project
Posted by "Nils Winkler (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=136181#action_136181 ]
nwinkler edited comment on MRELEASE-322 at 5/26/08 11:13 AM:
-----------------------------------------------------------------
I am facing the same problem. Did some work on this, please have a look at the two attached patches. Here's what they do (in addition to bumping up the version to 1.1-SNAPSHOT, which probably isn't that great - but it works to tell them apart from the official version):
h3. maven-release-plugin-flat.patch
* Moves the {{commitByProject}} attribute up to the {{AbstractReleaseMojo}} class. This way this attribute is available for both the prepare and the perform goals.
h3. maven-release-manager-flat.patch
* If the {{commitByProject}} parameter is set, the tagging also goes through the list of projects in the reactor and commits each one of them.
* During the perform phase, the working directory is set to the directory containing the parent POM, i.e. {{master/target/checkout/master}}
You can run this like this:
{code}
master> mvn -DcommitByProject=true release:prepare
master> mvn -DcommitByProject=true release:perform
{code}
The tag patch currently expects a SCM management layout like this - tested with SVN:
{code}
/project
+trunk
+master
+module-a
+module-b
+tags
+foo-1.0
+master
+module-a
+module-b
{code}
I have implemented it like this since it reflects our current environment. To use a different layout, I would recommed playing around with the code in {{ScmTagPhase.java}}. Maybe another parameter could be added to specify the SCM layout to use.
Hope this helps some of you.
was (Author: nwinkler):
I am facing the same problem. Did some work on this, please have a look at the two attached patches. Here's what they do (in addition to bumping up the version to 1.1-SNAPSHOT, which probably isn't that great - but it works to tell them apart from the official version):
.h2 maven-release-plugin-flat.patch
* Moves the {{commitByProject}} attribute up to the {{AbstractReleaseMojo}} class. This way this attribute is available for both the prepare and the perform goals.
.h2 maven-release-manager-flat.patch
* If the {{commitByProject}} parameter is set, the tagging also goes through the list of projects in the reactor and commits each one of them.
* During the perform phase, the working directory is set to the directory containing the parent POM, i.e. {{master/target/checkout/master}}
You can run this like this:
{code}
master> mvn -DcommitByProject=true release:prepare
master> mvn -DcommitByProject=true release:perform
{code}
The tag patch currently expects a SCM management layout like this - tested with SVN:
{code}
/project
+trunk
+master
+module-a
+module-b
+tags
+foo-1.0
+master
+module-a
+module-b
{code}
I have implemented it like this since it reflects our current environment. To use a different layout, I would recommed playing around with the code in {{ScmTagPhase.java}}. Maybe another parameter could be added to specify the SCM layout to use.
Hope this helps some of you.
> 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
> Attachments: maven-release-manager-flat.patch, maven-release-plugin-flat.patch
>
>
> 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
[jira] Closed: (MRELEASE-322) Unable to set the working directory
for projects where the master pom isn't at the root of the project
Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maria Odea Ching closed MRELEASE-322.
-------------------------------------
Resolution: Fixed
Fixed in trunk 778088. See MRELEASE-261
> 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
> Assignee: Maria Odea Ching
> Priority: Blocker
> Attachments: maven-release-manager-flat.patch, maven-release-plugin-flat.patch
>
>
> 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
[jira] Commented: (MRELEASE-322) Unable to set the working
directory for projects where the master pom isn't at the root of the
project
Posted by "Pavel Muller (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_125568 ]
Pavel Muller commented on MRELEASE-322:
---------------------------------------
I've got the same problem. Real blocker for our project.
> 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
[jira] Commented: (MRELEASE-322) Unable to set the working
directory for projects where the master pom isn't at the root of the
project
Posted by "Torben Giesselmann (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Commented: (MRELEASE-322) Unable to set the working
directory for projects where the master pom isn't at the root of the
project
Posted by "Paolo Compieta (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=131115#action_131115 ]
Paolo Compieta commented on MRELEASE-322:
-----------------------------------------
the 'commitByProject' option only affects commit, not tagging.
so we have separate commits for each module but only one tagging - for the parent project.
i designing just now the company-wide maven approach (we'll be using both Idea and Eclipse): this bug is really annoying - fix greatly appreciated.
Regards
Paolo
> 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