[
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
