You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Albert Kurucz (JIRA)" <ji...@codehaus.org> on 2010/10/17 07:20:32 UTC
[jira] Created: (MRELEASE-608) perform sets wrong working directory
when Executing goals 'deploy site-deploy' on SVN based project
perform sets wrong working directory when Executing goals 'deploy site-deploy' on SVN based project
---------------------------------------------------------------------------------------------------
Key: MRELEASE-608
URL: http://jira.codehaus.org/browse/MRELEASE-608
Project: Maven 2.x Release Plugin
Issue Type: Bug
Affects Versions: 2.1, 2.0
Environment: Linux, Maven 3.0
Reporter: Albert Kurucz
Priority: Blocker
Attachments: performWrongDir.txt
the perform goal, checks out the project from SVN to perform the release.
The project can be found, after this operation at
.../trunk/projectName/target/checkout/projectName/pom.xml
but after the checkout, the perform goal executes the goals 'deploy site-deploy' assuming that the project is here:
.../trunk/projectName/target/checkout/pom.xml
and fails, because it cannot find a pom there.
see log attached.
Find the actual open source project at https://svn.codehaus.org/jtstand/jtstand/trunk/jtstand/
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MRELEASE-608) perform sets wrong
working directory when Executing goals 'deploy site-deploy' on SVN based
project
Posted by "Dimitri Uwarov (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=239935#action_239935 ]
Dimitri Uwarov edited comment on MRELEASE-608 at 10/17/10 10:47 AM:
--------------------------------------------------------------------
Hi Albert,
both ways will do. By pointing to the exact svn location you ensure that pom.xml is being found. As i remember it is also the correct way to point to the project location, i.e. where the main pom is. Hence i dont think its a bug with m3.
// Dimitri
(See http://www.thinkplexx.com/learn/article/maven-learn-material/maven3/migration-from-maven2-to-maven3-roadmap-example-use-case-what-to-expect for the context of this ticket)
was (Author: neokrates):
Hi Albert,
both ways will do. By pointing to the exact svn location you ensure that pom.xml is being found. As i remember it is also the correct way to point to the project location, i.e. where the main pom is. Hence i dont think its a bug with m3.
// Dimitri
> perform sets wrong working directory when Executing goals 'deploy site-deploy' on SVN based project
> ---------------------------------------------------------------------------------------------------
>
> Key: MRELEASE-608
> URL: http://jira.codehaus.org/browse/MRELEASE-608
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Affects Versions: 2.0, 2.1
> Environment: Linux, Maven 3.0
> Reporter: Albert Kurucz
> Priority: Blocker
> Attachments: performWrongDir.txt
>
>
> the perform goal, checks out the project from SVN to perform the release.
> The project can be found, after this operation at
> .../trunk/projectName/target/checkout/projectName/pom.xml
> but after the checkout, the perform goal executes the goals 'deploy site-deploy' assuming that the project is here:
> .../trunk/projectName/target/checkout/pom.xml
> and fails, because it cannot find a pom there.
> see log attached.
> Find the actual open source project at https://svn.codehaus.org/jtstand/jtstand/trunk/jtstand/
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-608) perform sets wrong working
directory when Executing goals 'deploy site-deploy' on SVN based project
Posted by "Albert Kurucz (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=239949#action_239949 ]
Albert Kurucz commented on MRELEASE-608:
----------------------------------------
Both ways would have done, but I could not choose the connectionUrl way, because of poor documentation of that feature.
Not bug, hidden feature may be. Closing the issue, if you agree.
> perform sets wrong working directory when Executing goals 'deploy site-deploy' on SVN based project
> ---------------------------------------------------------------------------------------------------
>
> Key: MRELEASE-608
> URL: http://jira.codehaus.org/browse/MRELEASE-608
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Affects Versions: 2.0, 2.1
> Environment: Linux, Maven 3.0
> Reporter: Albert Kurucz
> Priority: Blocker
> Attachments: performWrongDir.txt
>
>
> the perform goal, checks out the project from SVN to perform the release.
> The project can be found, after this operation at
> .../trunk/projectName/target/checkout/projectName/pom.xml
> but after the checkout, the perform goal executes the goals 'deploy site-deploy' assuming that the project is here:
> .../trunk/projectName/target/checkout/pom.xml
> and fails, because it cannot find a pom there.
> see log attached.
> Find the actual open source project at https://svn.codehaus.org/jtstand/jtstand/trunk/jtstand/
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-608) perform sets wrong working
directory when Executing goals 'deploy site-deploy' on SVN based project
Posted by "Albert Kurucz (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=239931#action_239931 ]
Albert Kurucz commented on MRELEASE-608:
----------------------------------------
Dimitri,
Thanks for helping.
I have tried another way of fixing this:
Using
svn move
I have moved the project from trunk/projectName/pom.xml
to trunk/pom.xml
Not yet performed the release, but I am sure this will solve the problem.
I am not sure that the issue is a bug or not, because with Maven 2. the release:perform just worked. I don't know which version of the release plugin was used by that one (it did not enforce using <version> on the plugins as Maven 3 does.
Albert
> perform sets wrong working directory when Executing goals 'deploy site-deploy' on SVN based project
> ---------------------------------------------------------------------------------------------------
>
> Key: MRELEASE-608
> URL: http://jira.codehaus.org/browse/MRELEASE-608
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Affects Versions: 2.0, 2.1
> Environment: Linux, Maven 3.0
> Reporter: Albert Kurucz
> Priority: Blocker
> Attachments: performWrongDir.txt
>
>
> the perform goal, checks out the project from SVN to perform the release.
> The project can be found, after this operation at
> .../trunk/projectName/target/checkout/projectName/pom.xml
> but after the checkout, the perform goal executes the goals 'deploy site-deploy' assuming that the project is here:
> .../trunk/projectName/target/checkout/pom.xml
> and fails, because it cannot find a pom there.
> see log attached.
> Find the actual open source project at https://svn.codehaus.org/jtstand/jtstand/trunk/jtstand/
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-608) perform sets wrong working
directory when Executing goals 'deploy site-deploy' on SVN based project
Posted by "Dimitri Uwarov (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=239961#action_239961 ]
Dimitri Uwarov commented on MRELEASE-608:
-----------------------------------------
Sure, closed if solved.
As of connectionUrl, i would use two things to find out the parameters that should work and then the ones that really do work:
- http://maven.apache.org/plugins/maven-release-plugin/perform-mojo.html would give me the "connectionUrl" parameter, which should work;
- if it doesn't work i use the source of plugin to analyse. Normally, the "Source Repository" would give me what i need. Here, http://svn.apache.org/repos/asf/maven/scm/tags/maven-scm-1.4
// Dimitri
> perform sets wrong working directory when Executing goals 'deploy site-deploy' on SVN based project
> ---------------------------------------------------------------------------------------------------
>
> Key: MRELEASE-608
> URL: http://jira.codehaus.org/browse/MRELEASE-608
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Affects Versions: 2.0, 2.1
> Environment: Linux, Maven 3.0
> Reporter: Albert Kurucz
> Priority: Blocker
> Attachments: performWrongDir.txt
>
>
> the perform goal, checks out the project from SVN to perform the release.
> The project can be found, after this operation at
> .../trunk/projectName/target/checkout/projectName/pom.xml
> but after the checkout, the perform goal executes the goals 'deploy site-deploy' assuming that the project is here:
> .../trunk/projectName/target/checkout/pom.xml
> and fails, because it cannot find a pom there.
> see log attached.
> Find the actual open source project at https://svn.codehaus.org/jtstand/jtstand/trunk/jtstand/
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-608) perform sets wrong working
directory when Executing goals 'deploy site-deploy' on SVN based project
Posted by "Dimitri Uwarov (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=239935#action_239935 ]
Dimitri Uwarov commented on MRELEASE-608:
-----------------------------------------
Hi Albert,
both ways will do. By pointing to the exact svn location you ensure that pom.xml is being found. As i remember it is also the correct way to point to the project location, i.e. where the main pom is. Hence i dont think its a bug with m3.
// Dimitri
> perform sets wrong working directory when Executing goals 'deploy site-deploy' on SVN based project
> ---------------------------------------------------------------------------------------------------
>
> Key: MRELEASE-608
> URL: http://jira.codehaus.org/browse/MRELEASE-608
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Affects Versions: 2.0, 2.1
> Environment: Linux, Maven 3.0
> Reporter: Albert Kurucz
> Priority: Blocker
> Attachments: performWrongDir.txt
>
>
> the perform goal, checks out the project from SVN to perform the release.
> The project can be found, after this operation at
> .../trunk/projectName/target/checkout/projectName/pom.xml
> but after the checkout, the perform goal executes the goals 'deploy site-deploy' assuming that the project is here:
> .../trunk/projectName/target/checkout/pom.xml
> and fails, because it cannot find a pom there.
> see log attached.
> Find the actual open source project at https://svn.codehaus.org/jtstand/jtstand/trunk/jtstand/
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MRELEASE-608) perform sets wrong working directory
when Executing goals 'deploy site-deploy' on SVN based project
Posted by "Albert Kurucz (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Albert Kurucz closed MRELEASE-608.
----------------------------------
Resolution: Fixed
Use connectionUrl or move the project (and its POM) to trunk (from subdir of trunk), where it belongs any way.
> perform sets wrong working directory when Executing goals 'deploy site-deploy' on SVN based project
> ---------------------------------------------------------------------------------------------------
>
> Key: MRELEASE-608
> URL: http://jira.codehaus.org/browse/MRELEASE-608
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Affects Versions: 2.0, 2.1
> Environment: Linux, Maven 3.0
> Reporter: Albert Kurucz
> Priority: Blocker
> Attachments: performWrongDir.txt
>
>
> the perform goal, checks out the project from SVN to perform the release.
> The project can be found, after this operation at
> .../trunk/projectName/target/checkout/projectName/pom.xml
> but after the checkout, the perform goal executes the goals 'deploy site-deploy' assuming that the project is here:
> .../trunk/projectName/target/checkout/pom.xml
> and fails, because it cannot find a pom there.
> see log attached.
> Find the actual open source project at https://svn.codehaus.org/jtstand/jtstand/trunk/jtstand/
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MRELEASE-608) perform sets wrong
working directory when Executing goals 'deploy site-deploy' on SVN based
project
Posted by "Dimitri Uwarov (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=239929#action_239929 ]
Dimitri Uwarov edited comment on MRELEASE-608 at 10/17/10 8:08 AM:
-------------------------------------------------------------------
Hi Albert
The project is checked out correctly from the location you specified (https://svn.codehaus.org/jtstand/jtstand/tags/jtstand-1.2.5). But the actual pom is in /home/albert/ch/jtstand/jtstand/trunk/jtstand/target/checkout/jtstand. I guess you should try to change the connectionUrl to https://svn.codehaus.org/jtstand/jtstand/tags/jtstand-1.2.5/jtstand.
It worked for me with jtstand 1.2.6-SNAPSHOT from trunk
// Dimitri
was (Author: neokrates):
Hi Albert
The proect is checked out correctly from the location you specified (https://svn.codehaus.org/jtstand/jtstand/tags/jtstand-1.2.5). But the actual pom is in /home/albert/ch/jtstand/jtstand/trunk/jtstand/target/checkout/jtstand. I guess you should try to change the connectionUrl to https://svn.codehaus.org/jtstand/jtstand/tags/jtstand-1.2.5/jtstand.
It worked for me with jtstand 1.2.6-SNAPSHOT from trunk
// Dimitri
> perform sets wrong working directory when Executing goals 'deploy site-deploy' on SVN based project
> ---------------------------------------------------------------------------------------------------
>
> Key: MRELEASE-608
> URL: http://jira.codehaus.org/browse/MRELEASE-608
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Affects Versions: 2.0, 2.1
> Environment: Linux, Maven 3.0
> Reporter: Albert Kurucz
> Priority: Blocker
> Attachments: performWrongDir.txt
>
>
> the perform goal, checks out the project from SVN to perform the release.
> The project can be found, after this operation at
> .../trunk/projectName/target/checkout/projectName/pom.xml
> but after the checkout, the perform goal executes the goals 'deploy site-deploy' assuming that the project is here:
> .../trunk/projectName/target/checkout/pom.xml
> and fails, because it cannot find a pom there.
> see log attached.
> Find the actual open source project at https://svn.codehaus.org/jtstand/jtstand/trunk/jtstand/
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-608) perform sets wrong working
directory when Executing goals 'deploy site-deploy' on SVN based project
Posted by "Dimitri Uwarov (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=239929#action_239929 ]
Dimitri Uwarov commented on MRELEASE-608:
-----------------------------------------
Hi Albert
The proect is checked out correctly from the location you specified (https://svn.codehaus.org/jtstand/jtstand/tags/jtstand-1.2.5). But the actual pom is in /home/albert/ch/jtstand/jtstand/trunk/jtstand/target/checkout/jtstand. I guess you should try to change the connectionUrl to https://svn.codehaus.org/jtstand/jtstand/tags/jtstand-1.2.5/jtstand.
It worked for me with jtstand 1.2.6-SNAPSHOT from trunk
// Dimitri
> perform sets wrong working directory when Executing goals 'deploy site-deploy' on SVN based project
> ---------------------------------------------------------------------------------------------------
>
> Key: MRELEASE-608
> URL: http://jira.codehaus.org/browse/MRELEASE-608
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Affects Versions: 2.0, 2.1
> Environment: Linux, Maven 3.0
> Reporter: Albert Kurucz
> Priority: Blocker
> Attachments: performWrongDir.txt
>
>
> the perform goal, checks out the project from SVN to perform the release.
> The project can be found, after this operation at
> .../trunk/projectName/target/checkout/projectName/pom.xml
> but after the checkout, the perform goal executes the goals 'deploy site-deploy' assuming that the project is here:
> .../trunk/projectName/target/checkout/pom.xml
> and fails, because it cannot find a pom there.
> see log attached.
> Find the actual open source project at https://svn.codehaus.org/jtstand/jtstand/trunk/jtstand/
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira