[
https://jira.codehaus.org/browse/MRELEASE-727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominik Bartholdi updated MRELEASE-727:
---------------------------------------
Attachment: flat-project-layout.patch
This patch fixes the issue for flat project layouts.
All tests still run successfully.
All I did was to remove a line in the current RunPerformGoalsPhase code. It was
assumed, that if the parent pom was in a subdirectory, then the SCM checkout
directory would be in the parent directory if that pom, but for flat projects,
that's not right... :)
> release plugin uses wrong checkout directory
> --------------------------------------------
>
> Key: MRELEASE-727
> URL: https://jira.codehaus.org/browse/MRELEASE-727
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: perform
> Affects Versions: 2.2, 2.2.2
> Environment: mvn 3.0.3
> Reporter: Dominik Bartholdi
> Priority: Blocker
> Attachments: flat-project-layout.patch, release_failed.txt,
> testproject.zip
>
>
> When performing a release build on a multi module project, the plugin uses a
> wrong checkout directory and therefore is unable to perform the release.
> I tested this with both version 2.2 and 2.2.2
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-release-plugin:2.2.2:perform (default-cli) on
> project test_multi_parent: Error executing Maven. Working directory
> "/Users/domi/work/ws/sts_0/test_multi_parent/target/checkout/test_multi_parent/test_multi_parent"
> does not exist! -> [Help 1]
> We use flat project structure (where parent and modul project are in the same
> directory)
> The SVN Repo looks like this:
> .../svnrepos/KUQ/trunk/test_multi_parent
> .../svnrepos/KUQ/trunk/test_multi_module1
> I'll attache a minimal test project to reproduce it and a file containing the
> whole log output for release:prepare and release:perform
> To reproduce the problem:
> - adjust the SVN paths in the pom.xml
> - checkin to SVN
> - release:prepare
> - release:perform -Dgoals=install
--
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
