You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Vadim Tsing (JIRA)" <ji...@codehaus.org> on 2011/08/23 20:45:32 UTC
[jira] Created: (MRELEASE-705) Project directory appended twice
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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-705) Project directory appended twice
Posted by "Vadim Tsing (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=292469#comment-292469 ]
Vadim Tsing commented on MRELEASE-705:
--------------------------------------
{noformat}
Apache Maven 2.2.1 (r801777; 2009-08-06 15:16:01-0400)
Java version: 1.6.0_29
Java home: C:\Java\jdk1.6.0_29\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 7" version: "6.1" arch: "x86" Family: "windows"
{noformat}
> 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
[jira] (MRELEASE-705) Project directory appended twice
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] (MRELEASE-705) Project directory appended twice
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte closed MRELEASE-705.
-----------------------------------
Resolution: Incomplete
I see no reply on Marks question, so I'll close this as incomplete, hoping it's indeed a duplicate.
> 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, 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
[jira] (MRELEASE-705) Project directory appended twice
Posted by "Andrey Taranov (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] (MRELEASE-705) Project directory appended twice
Posted by "Andrey Taranov (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=297949#comment-297949 ]
Andrey Taranov commented on MRELEASE-705:
-----------------------------------------
So I'm sequentially trying all versions:
- maven-release-plugin:2.0 works OK
- maven-release-plugin:2.1 works OK
- maven-release-plugin:2.2 doesn't work
> 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
[jira] (MRELEASE-705) Project directory appended twice
Posted by "Mark Struberg (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=297972#comment-297972 ]
Mark Struberg commented on MRELEASE-705:
----------------------------------------
This could be a duplicate of MRELEASE-727 , wdyt?
> 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, 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
[jira] (MRELEASE-705) Project directory appended twice
Posted by "Andrey Taranov (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=297951#comment-297951 ]
Andrey Taranov commented on MRELEASE-705:
-----------------------------------------
Here is the log for version 2.2 release goal.
Notice the second warning:
bq. *Base directory is a file. Using base directory as POM location.*
This was not present in version 2.1.
Also notice the error message:
bq. *Working directory "C:\dev\spikes-local\mvnrelease-flat\parent\target\checkout\parent\parent" does not exist!*
The last directory is duplicated!
{noformat}
C:\dev\spikes-local\mvnrelease-flat\parent>mvn release:perform -Dmaven.scm.provider.cvs.implementation=cvs_native -DcommitByProject=true
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Build Order:
[INFO]
[INFO] parent
[INFO] first-jar
[INFO] second-jar
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building parent 1.11-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-release-plugin:2.2:perform (default-cli) @ parent ---
[INFO] Checking out the project to perform the release ...
[INFO] Executing: cmd.exe /X /C "cvs -z3 -f -d :local:d:\cvsroot -q checkout -r parent-1_10-SNAPSHOT -d checkout mvnrelease-flat"
[INFO] Working directory: C:\dev\spikes-local\mvnrelease-flat\parent\target
[INFO] Invoking perform goals in directory C:\dev\spikes-local\mvnrelease-flat\parent\target\checkout\parent
[INFO] Executing goals 'deploy'...
[WARNING] Base directory is a file. Using base directory as POM location.
[WARNING] Maven will be executed in interactive mode, but no input stream has been configured for this MavenInvoker instance.
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] parent ............................................ FAILURE [2.300s]
[INFO] first-jar ......................................... SKIPPED
[INFO] second-jar ........................................ SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2.572s
[INFO] Finished at: Sat May 05 22:59:16 GMT+04:00 2012
[INFO] Final Memory: 5M/15M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.2:perform (default-cli) on project parent: Error executing Maven. Working directory "C:\dev\spikes-local\mvnrelease-flat\parent\target\checkout\parent\parent" does not exist! -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
{noformat}
> 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
[jira] (MRELEASE-705) Project directory appended twice
Posted by "Andrey Taranov (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=296391#comment-296391 ]
Andrey Taranov commented on MRELEASE-705:
-----------------------------------------
I'm currently using Maven 3.0.3, so I assume the problem is entirely with maven-release-plugin.
I will try to reproduce with different versions beetween 2.0 and 2.2.2 and post the logs here. I will also upload a minimal test project I use.
> 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
[jira] (MRELEASE-705) Project directory appended twice
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte updated MRELEASE-705:
------------------------------------
Description:
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.
was:
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.
Affects Version/s: 2.2
> 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, 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
[jira] (MRELEASE-705) Project directory appended twice
Posted by "Andrey Taranov (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=297950#comment-297950 ]
Andrey Taranov commented on MRELEASE-705:
-----------------------------------------
Here is a log fragment from version 2.1 release goal:
{noformat}
C:\dev\spikes-local\mvnrelease-flat\parent>mvn release:perform -Dmaven.scm.provider.cvs.implementation=cvs_native -DcommitByProject=true
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Build Order:
[INFO]
[INFO] parent
[INFO] first-jar
[INFO] second-jar
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building parent 1.10-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-release-plugin:2.1:perform (default-cli) @ parent ---
[INFO] Checking out the project to perform the release ...
[INFO] Executing: cmd.exe /X /C "cvs -z3 -f -d :local:d:\cvsroot -q checkout -r parent-1_9 -d checkout mvnrelease-flat"
[INFO] Working directory: C:\dev\spikes-local\mvnrelease-flat\parent\target
[INFO] Executing goals 'deploy'...
{noformat}
> 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
[jira] (MRELEASE-705) Project directory appended twice
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ 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