[MRELEASE-168] All submodule projects must be from the same subversion repository

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0-beta-4
• Fix Version/s: 2.0-beta-5
• Component/s: scm
• Assignee: Emmanuel Venisse
• Reporter: Michael Semb Wever
• Created: 02/Oct/06 10:10
• Updated: 17/Sep/07 06:27
• Resolved: 24/Apr/07 08:40

Description

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.

Issue Links

• relates to: MRELEASE-6 Multiproject Release: No check in