Maven 2.x Release Plugin

Specifying workingDirectory as system property on CL is not picked up by release:perform

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 2.0-beta-7
  • Fix Version/s: 2.0-beta-8
  • Component/s: scm
  • Labels:
    None
  • Environment:
    Win XP SP2, SUN JDK 1.5.0_16-b02, mvn 2.1.0-M1
  • Number of attachments :
    0

Description

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

Activity

Hide
Anders Hammar added a comment -

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>

Show
Anders Hammar added a comment - 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>
Hide
Benjamin Bentmann added a comment -

Fixed in r707479, snapshot deployed.

Show
Benjamin Bentmann added a comment - Fixed in r707479, snapshot deployed.
Hide
Anders Hammar added a comment -

Amazing speed on the fix, many thanks!

Show
Anders Hammar added a comment - Amazing speed on the fix, many thanks!
Hide
Benjamin Bentmann added a comment -

If just everything would be as easy to fix as this one

Show
Benjamin Bentmann added a comment - If just everything would be as easy to fix as this one

People

Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved: