[
https://jira.codehaus.org/browse/MRELEASE-705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=292467#comment-292467
]
Robert Scholte commented on MRELEASE-705:
-----------------------------------------
{quote}
[WARNING] Base directory is a file. Using base directory as POM location.
[DEBUG] Specified POM file is not named 'pom.xml'. Using the '-f' command-line
option to accommodate non-standard filename...
[DEBUG] Executing: cmd.exe /X /C "C:\java\apache-maven-2.2.1\bin\mvn.bat -X -D
maven.repo.local=C:\Users\vadim\.m2\repository -f test-project-1 -D
performRelease=true -P artifactory deploy"
{quote}
These lines interest me. Do you have any clue why base directory is a file on
not a directory? This is probably the root of the problem.
Could you attach your environment? (result of {{mvn -v}}
> 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
