[
http://jira.codehaus.org/browse/MRELEASE-394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=156876#action_156876
]
Petr Kozelka commented on MRELEASE-394:
---------------------------------------
I just confirm that the same happens to me too, observed since 12.11.2008 - but
only on multimodule releases.
For some strange reason, releasing single modules works fine.
My svn client is version 1.5.4, running against SVN repositories at
sourceforge.net and assembla com.
Using maven-2.0.9, java-1.6.0_10, Gentoo Linux on x86.
> Support for SCM update after each commit
> ----------------------------------------
>
> Key: MRELEASE-394
> URL: http://jira.codehaus.org/browse/MRELEASE-394
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Components: scm
> Affects Versions: 2.0-beta-8
> Environment: Windows Vista SP1 + JDK 1.5 + Mvn 2.0.9 and
> Ubuntu 8.04 Server + JDK 1.5 + Mvn 2.0.8
> Reporter: rahul somasunderam
>
> I have a multi module project and currently I have to do
> >>svn co http://svnrepo/project/trunk
> >>mvn release:prepare
> At this stage it fails
> >>svn up
> >>mvn release:prepare
> Now it is complete.
> It would be good to have a hook to get the svn update to happen after each
> svn commit performed by the release plugin
--
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
