[
http://jira.codehaus.org/browse/MREACTOR-7?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Fabulich updated MREACTOR-7:
--------------------------------
Fix Version/s: Future
> reactor:resume can run projects in the wrong order
> --------------------------------------------------
>
> Key: MREACTOR-7
> URL: http://jira.codehaus.org/browse/MREACTOR-7
> Project: Maven 2.x Reactor Plugin
> Issue Type: Bug
> Affects Versions: 1.0
> Reporter: Dan Fabulich
> Fix For: Future
>
>
> reactor:resume works by passing a list of includes to mvn, like this: "mvn
> --reactor -D maven.reactor.includes=foo/pom.xml,bar/pom.xml,baz/pom.xml".
> However, unlike a temporary POM file which guarantees a stable ordering,
> reactor.includes is just an include list; Maven can run the projects in any
> order it likes. By default, this is the order in which directories are
> discovered on the filesystem; this is typically alphabetically ordered.
> So if you've got three independent modules in your POM like this:
> {code}
> <modules>
> <module>One</module>
> <module>Two</module>
> <module>Three</module>
> </modules>
> {code}
> and you try to resume from Two (skipping One), we'll run "mvn -reactor -D
> maven.reactor.includes=Two/pom.xml,Three/pom.xml". But when Maven discovers
> these directories in alphabetical order, it will run Three first and then Two
> (because Three comes before Two in alphabetical ordering).
> The workaround is to make sure that your module list in your POM is the same
> order that Maven will discover the files on the filesystem, i.e. in
> alphabetical order.
--
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
