[
https://jira.codehaus.org/browse/MRELEASE-705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=296256#comment-296256
]
Andrey Taranov commented on MRELEASE-705:
-----------------------------------------
I'm having exact same problem described by Vadim. We use CVS so the fixes in
MRELEASE-457 are irrelevant.
Have configured the parent POM to use maven-release-plugin:2.0 and the problem
was solved.
> Project directory appended twice
> --------------------------------
>
> Key: MRELEASE-705
> URL: https://jira.codehaus.org/browse/MRELEASE-705
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: perform
> Affects Versions: 2.2.1
> Environment: accurev scm provider
> Reporter: Vadim Tsing
> Priority: Blocker
> Attachments: output.txt
>
>
> During perform, the fix for MRELEASE-457 changes the checkout directory by
> appending the checkout path, later the release manager appends it again in
> determineWorkingDirectory(). As a result maven cannot find the checked out
> project.
> Please see attached log file with -X output, specifically line 1541 that
> shows the correct project path, however, when it comes to running the deploy
> command, it appends project path again as indicated by line 1553.
--
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
