maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Semb Wever (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MRELEASE-168) All submodule projects must be from the same subversion repository
Date Mon, 02 Oct 2006 15:12:26 GMT
    [ http://jira.codehaus.org/browse/MRELEASE-168?page=comments#action_76315 ] 
            
Michael Semb Wever commented on MRELEASE-168:
---------------------------------------------

Typo: "But if they are not,"
should be 
"If they are not,"

> 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
>
> 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

        

Mime
View raw message