[ http://jira.codehaus.org/browse/MRELEASE-168?page=all ]
Michael Semb Wever updated MRELEASE-168:
----------------------------------------
Attachment: MRELEASE-168.patch
Initial patch. One test commented out. (The test only tested that the scm
commit was only performed once which this issue intentonally changes).
> All submodule projects must be from the same subversion repository
> ------------------------------------------------------------------
>
> Key: MRELEASE-168
> URL: http://jira.codehaus.org/browse/MRELEASE-168
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Affects Versions: 2.0-beta-4
> Reporter: Michael Semb Wever
> Attachments: MRELEASE-168.patch
>
>
> It is too restrictive to expect that all modules in a maven project will be
> from the same subversion repository.
> But if they are not, when "mvn release:prepare" runs, edits all the pom.xml
> file, then goes to check them in, it fails.
> The check in command looks something like "svn ci pom.xml a/pom.xml b/pom.xml
> c/pom.xml" where a, b, and c are modules listed in the first pom.xml.
> I'd expect it would be very simple and easy to change the way this command
> ran, so that it ran a separate "svn ci ..." for each pom file, thus allowing
> cross- subversion repository modules to exist and be supported by this plugin.
> We'd like this fixed pretty quickly, so if you could lead to as to which file
> I can start getting my teeth stuck into, i'd hopefully submit a patch asap.
--
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
