You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Anders Hammar (JIRA)" <ji...@codehaus.org> on 2008/10/22 16:40:19 UTC
[jira] Created: (MRELEASE-382) Specifying workingDirectory as
system property on CL is not picked up by release:perform
Specifying workingDirectory as system property on CL is not picked up by release:perform
----------------------------------------------------------------------------------------
Key: MRELEASE-382
URL: http://jira.codehaus.org/browse/MRELEASE-382
Project: Maven 2.x Release Plugin
Issue Type: Bug
Components: scm
Affects Versions: 2.0-beta-7
Environment: Win XP SP2, SUN JDK 1.5.0_16-b02, mvn 2.1.0-M1
Reporter: Anders Hammar
Running the release:perform mojo from command line in an empty directory (no pom) with the -DworkingDirectory flag, the specified workingDirectory is not picked up. This results in the workingDirectory being used something like 'CUR_DIR/null/target/checkout'.
The command being issued:
mvn release:perform -DconnectionUrl="scm:clearcase:VIEW_NAME:load /VOB/PATH" -Dtag=TAG_NAME -DworkingDirectory=c:\mvn-test\checkout
--
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-382) Specifying workingDirectory as
system property on CL is not picked up by release:perform
Posted by "Anders Hammar (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=151785#action_151785 ]
Anders Hammar commented on MRELEASE-382:
----------------------------------------
Amazing speed on the fix, many thanks!
> Specifying workingDirectory as system property on CL is not picked up by release:perform
> ----------------------------------------------------------------------------------------
>
> Key: MRELEASE-382
> URL: http://jira.codehaus.org/browse/MRELEASE-382
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Components: scm
> Affects Versions: 2.0-beta-7
> Environment: Win XP SP2, SUN JDK 1.5.0_16-b02, mvn 2.1.0-M1
> Reporter: Anders Hammar
> Assignee: Benjamin Bentmann
> Fix For: 2.0-beta-8
>
>
> Running the release:perform mojo from command line in an empty directory (no pom) with the -DworkingDirectory flag, the specified workingDirectory is not picked up. This results in the workingDirectory being used something like 'CUR_DIR/null/target/checkout'.
> The command being issued:
> mvn release:perform -DconnectionUrl="scm:clearcase:VIEW_NAME:load /VOB/PATH" -Dtag=TAG_NAME -DworkingDirectory=c:\mvn-test\checkout
--
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-382) Specifying workingDirectory as
system property on CL is not picked up by release:perform
Posted by "Anders Hammar (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=151583#action_151583 ]
Anders Hammar commented on MRELEASE-382:
----------------------------------------
If I have a pom in the current directory in which I specify workingDirectory (see below) it works. Why not from command line?
<project>
<modelVersion>4.0.0</modelVersion>
<groupId>a.b.c.maven.dev</groupId>
<artifactId>release-test</artifactId>
<packaging>pom</packaging>
<version>1.0-SNAPSHOT</version>
<name>Test of release</name>
<build>
<pluginManagement>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-release-plugin</artifactId>
<version>2.0-beta-7</version>
<configuration>
<workingDirectory>c:\mvn-release</workingDirectory>
</configuration>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-scm-plugin</artifactId>
<version>1.1</version>
</plugin>
</plugins>
</pluginManagement>
</build>
</project>
> Specifying workingDirectory as system property on CL is not picked up by release:perform
> ----------------------------------------------------------------------------------------
>
> Key: MRELEASE-382
> URL: http://jira.codehaus.org/browse/MRELEASE-382
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: scm
> Affects Versions: 2.0-beta-7
> Environment: Win XP SP2, SUN JDK 1.5.0_16-b02, mvn 2.1.0-M1
> Reporter: Anders Hammar
>
> Running the release:perform mojo from command line in an empty directory (no pom) with the -DworkingDirectory flag, the specified workingDirectory is not picked up. This results in the workingDirectory being used something like 'CUR_DIR/null/target/checkout'.
> The command being issued:
> mvn release:perform -DconnectionUrl="scm:clearcase:VIEW_NAME:load /VOB/PATH" -Dtag=TAG_NAME -DworkingDirectory=c:\mvn-test\checkout
--
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-382) Specifying workingDirectory as
system property on CL is not picked up by release:perform
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann updated MRELEASE-382:
---------------------------------------
Issue Type: Improvement (was: Bug)
> Specifying workingDirectory as system property on CL is not picked up by release:perform
> ----------------------------------------------------------------------------------------
>
> Key: MRELEASE-382
> URL: http://jira.codehaus.org/browse/MRELEASE-382
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Components: scm
> Affects Versions: 2.0-beta-7
> Environment: Win XP SP2, SUN JDK 1.5.0_16-b02, mvn 2.1.0-M1
> Reporter: Anders Hammar
>
> Running the release:perform mojo from command line in an empty directory (no pom) with the -DworkingDirectory flag, the specified workingDirectory is not picked up. This results in the workingDirectory being used something like 'CUR_DIR/null/target/checkout'.
> The command being issued:
> mvn release:perform -DconnectionUrl="scm:clearcase:VIEW_NAME:load /VOB/PATH" -Dtag=TAG_NAME -DworkingDirectory=c:\mvn-test\checkout
--
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-382) Specifying workingDirectory as
system property on CL is not picked up by release:perform
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=151789#action_151789 ]
Benjamin Bentmann commented on MRELEASE-382:
--------------------------------------------
If just everything would be as easy to fix as this one ;-)
> Specifying workingDirectory as system property on CL is not picked up by release:perform
> ----------------------------------------------------------------------------------------
>
> Key: MRELEASE-382
> URL: http://jira.codehaus.org/browse/MRELEASE-382
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Components: scm
> Affects Versions: 2.0-beta-7
> Environment: Win XP SP2, SUN JDK 1.5.0_16-b02, mvn 2.1.0-M1
> Reporter: Anders Hammar
> Assignee: Benjamin Bentmann
> Fix For: 2.0-beta-8
>
>
> Running the release:perform mojo from command line in an empty directory (no pom) with the -DworkingDirectory flag, the specified workingDirectory is not picked up. This results in the workingDirectory being used something like 'CUR_DIR/null/target/checkout'.
> The command being issued:
> mvn release:perform -DconnectionUrl="scm:clearcase:VIEW_NAME:load /VOB/PATH" -Dtag=TAG_NAME -DworkingDirectory=c:\mvn-test\checkout
--
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-382) Specifying workingDirectory as system
property on CL is not picked up by release:perform
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann closed MRELEASE-382.
--------------------------------------
Assignee: Benjamin Bentmann
Resolution: Fixed
Fix Version/s: 2.0-beta-8
Fixed in [r707479|http://svn.apache.org/viewvc?view=rev&revision=707479], snapshot deployed.
> Specifying workingDirectory as system property on CL is not picked up by release:perform
> ----------------------------------------------------------------------------------------
>
> Key: MRELEASE-382
> URL: http://jira.codehaus.org/browse/MRELEASE-382
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Components: scm
> Affects Versions: 2.0-beta-7
> Environment: Win XP SP2, SUN JDK 1.5.0_16-b02, mvn 2.1.0-M1
> Reporter: Anders Hammar
> Assignee: Benjamin Bentmann
> Fix For: 2.0-beta-8
>
>
> Running the release:perform mojo from command line in an empty directory (no pom) with the -DworkingDirectory flag, the specified workingDirectory is not picked up. This results in the workingDirectory being used something like 'CUR_DIR/null/target/checkout'.
> The command being issued:
> mvn release:perform -DconnectionUrl="scm:clearcase:VIEW_NAME:load /VOB/PATH" -Dtag=TAG_NAME -DworkingDirectory=c:\mvn-test\checkout
--
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