You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Philipp Paland (JIRA)" <ji...@codehaus.org> on 2012/01/10 16:02:02 UTC
[jira] (MRELEASE-725) Releasing a specific module-based project
fails (Regression from 2.1)
Philipp Paland created MRELEASE-725:
---------------------------------------
Summary: Releasing a specific module-based project fails (Regression from 2.1)
Key: MRELEASE-725
URL: https://jira.codehaus.org/browse/MRELEASE-725
Project: Maven 2.x Release Plugin
Issue Type: Bug
Affects Versions: 2.2.2, 2.2.1, 2.2
Environment: Mac OS X 10.7.2
Apache Maven 3.0.3
Subversion 1.6.16 (r1073529)
Reporter: Philipp Paland
Attachments: transscript.txt, trunk.zip
We can not release our project with a version of the release plugin greater than 2.1.
I have distilled the problem to a small example project (attached as zip). The project has a core module (with code) and an aggregating build project, like this:
-> build
-> release
-> pom.xml
-> core
-> hello-world
-> pom.xml
-> src/main/java/HelloWorld.java
where "hello-world" is a module of "release".
It looks like release:perform tries to build in the wrong directory:
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.2.2:perform (default-cli) on project release: Error executing Maven. Working directory "/Development/maven-release-bug/trunk/build/release/target/checkout/build/release/build/release" does not exist! -> [Help 1]
I have also attached a transscript with some easy steps to reproduce the problem. First, a local svn repo is created. Then, the working release with 2.1 is demonstrated. Then the plugin version in the pom is changed and the error is shown.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-725) Releasing a specific module-based project
fails (Regression from 2.1)
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=298678#comment-298678 ]
Robert Scholte commented on MRELEASE-725:
-----------------------------------------
@Philipp, could you try this with the maven-release-plugin version 2.3? This version contains some fixes related to the path of the working directory.
> Releasing a specific module-based project fails (Regression from 2.1)
> ---------------------------------------------------------------------
>
> Key: MRELEASE-725
> URL: https://jira.codehaus.org/browse/MRELEASE-725
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: perform
> Affects Versions: 2.2, 2.2.1, 2.2.2
> Environment: Mac OS X 10.7.2
> Apache Maven 3.0.3
> Subversion 1.6.16 (r1073529)
> Reporter: Philipp Paland
> Attachments: transscript.txt, trunk.zip
>
>
> We can not release our project with a version of the release plugin greater than 2.1.
> I have distilled the problem to a small example project (attached as zip). The project has a core module (with code) and an aggregating build project, like this:
> -> build
> -> release
> -> pom.xml
> -> core
> -> hello-world
> -> pom.xml
> -> src/main/java/HelloWorld.java
> where "hello-world" is a module of "release".
> It looks like release:perform tries to build in the wrong directory:
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.2.2:perform (default-cli) on project release: Error executing Maven. Working directory "/Development/maven-release-bug/trunk/build/release/target/checkout/build/release/build/release" does not exist! -> [Help 1]
> I have also attached a transscript with some easy steps to reproduce the problem. First, a local svn repo is created. Then, the working release with 2.1 is demonstrated. Then the plugin version in the pom is changed and the error is shown.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-725) Releasing a specific module-based project
fails (Regression from 2.1)
Posted by "Philipp Paland (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Philipp Paland closed MRELEASE-725.
-----------------------------------
Resolution: Fixed
Fix Version/s: 2.3
This is fixed in 2.3
> Releasing a specific module-based project fails (Regression from 2.1)
> ---------------------------------------------------------------------
>
> Key: MRELEASE-725
> URL: https://jira.codehaus.org/browse/MRELEASE-725
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: perform
> Affects Versions: 2.2, 2.2.1, 2.2.2
> Environment: Mac OS X 10.7.2
> Apache Maven 3.0.3
> Subversion 1.6.16 (r1073529)
> Reporter: Philipp Paland
> Fix For: 2.3
>
> Attachments: transscript.txt, trunk.zip
>
>
> We can not release our project with a version of the release plugin greater than 2.1.
> I have distilled the problem to a small example project (attached as zip). The project has a core module (with code) and an aggregating build project, like this:
> -> build
> -> release
> -> pom.xml
> -> core
> -> hello-world
> -> pom.xml
> -> src/main/java/HelloWorld.java
> where "hello-world" is a module of "release".
> It looks like release:perform tries to build in the wrong directory:
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.2.2:perform (default-cli) on project release: Error executing Maven. Working directory "/Development/maven-release-bug/trunk/build/release/target/checkout/build/release/build/release" does not exist! -> [Help 1]
> I have also attached a transscript with some easy steps to reproduce the problem. First, a local svn repo is created. Then, the working release with 2.1 is demonstrated. Then the plugin version in the pom is changed and the error is shown.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-725) Releasing a specific module-based project
fails (Regression from 2.1)
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte updated MRELEASE-725:
------------------------------------
Component/s: perform
> Releasing a specific module-based project fails (Regression from 2.1)
> ---------------------------------------------------------------------
>
> Key: MRELEASE-725
> URL: https://jira.codehaus.org/browse/MRELEASE-725
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: perform
> Affects Versions: 2.2, 2.2.1, 2.2.2
> Environment: Mac OS X 10.7.2
> Apache Maven 3.0.3
> Subversion 1.6.16 (r1073529)
> Reporter: Philipp Paland
> Attachments: transscript.txt, trunk.zip
>
>
> We can not release our project with a version of the release plugin greater than 2.1.
> I have distilled the problem to a small example project (attached as zip). The project has a core module (with code) and an aggregating build project, like this:
> -> build
> -> release
> -> pom.xml
> -> core
> -> hello-world
> -> pom.xml
> -> src/main/java/HelloWorld.java
> where "hello-world" is a module of "release".
> It looks like release:perform tries to build in the wrong directory:
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.2.2:perform (default-cli) on project release: Error executing Maven. Working directory "/Development/maven-release-bug/trunk/build/release/target/checkout/build/release/build/release" does not exist! -> [Help 1]
> I have also attached a transscript with some easy steps to reproduce the problem. First, a local svn repo is created. Then, the working release with 2.1 is demonstrated. Then the plugin version in the pom is changed and the error is shown.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-725) Releasing a specific module-based project
fails (Regression from 2.1)
Posted by "Philipp Paland (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=287910#comment-287910 ]
Philipp Paland commented on MRELEASE-725:
-----------------------------------------
Whitespace correction:
-> build
--> release
---> pom.xml
-> core
--> hello-world
---> pom.xml
---> src/main/java/HelloWorld.java
> Releasing a specific module-based project fails (Regression from 2.1)
> ---------------------------------------------------------------------
>
> Key: MRELEASE-725
> URL: https://jira.codehaus.org/browse/MRELEASE-725
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Affects Versions: 2.2, 2.2.1, 2.2.2
> Environment: Mac OS X 10.7.2
> Apache Maven 3.0.3
> Subversion 1.6.16 (r1073529)
> Reporter: Philipp Paland
> Attachments: transscript.txt, trunk.zip
>
>
> We can not release our project with a version of the release plugin greater than 2.1.
> I have distilled the problem to a small example project (attached as zip). The project has a core module (with code) and an aggregating build project, like this:
> -> build
> -> release
> -> pom.xml
> -> core
> -> hello-world
> -> pom.xml
> -> src/main/java/HelloWorld.java
> where "hello-world" is a module of "release".
> It looks like release:perform tries to build in the wrong directory:
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.2.2:perform (default-cli) on project release: Error executing Maven. Working directory "/Development/maven-release-bug/trunk/build/release/target/checkout/build/release/build/release" does not exist! -> [Help 1]
> I have also attached a transscript with some easy steps to reproduce the problem. First, a local svn repo is created. Then, the working release with 2.1 is demonstrated. Then the plugin version in the pom is changed and the error is shown.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira