[
https://jira.codehaus.org/browse/MRELEASE-705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=296352#comment-296352
]
Robert Scholte commented on MRELEASE-705:
-----------------------------------------
Based on only the output above it is not possible to reproduce this issue.
According to the logging the base directory is called {{test-project-1}} (I
think), but this seems to be a file and not a directory. I still think we have
to find the real cause around here.
Andrey, it would be nice if you could figure out with which version this bug
was introduced (the gap between 2.0 and 2.2.2, if you have tried this version,
is huge).
Also: Is this also an issue for Maven3?
> 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
