[
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
