[jira] Updated: (MREACTOR-1) Reactor plugin doesn't work with sibling aggregated modules

["Dan Fabulich (JIRA)" <ji...@codehaus.org>]

     [ http://jira.codehaus.org/browse/MREACTOR-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dan Fabulich updated MREACTOR-1:
--------------------------------

    Fix Version/s: Future

> Reactor plugin doesn't work with sibling aggregated modules
> -----------------------------------------------------------
>
>                 Key: MREACTOR-1
>                 URL: http://jira.codehaus.org/browse/MREACTOR-1
>             Project: Maven 2.x Reactor Plugin
>          Issue Type: Bug
>    Affects Versions: Future
>            Reporter: Dan Fabulich
>             Fix For: Future
>
>
> Normally when you have an aggregator POM with a list of <modules>, the element lists out subdirectories of the aggregator, like this:
> {code}
> <modules>
>   <module>foo</module>
>   <module>bar</module>
> </modules>
> {code}
> But modules can be anywhere; the module list can declare relative paths to anywhere, like this:
> {code}
> <modules>
>   <module>../foo</module>
>   <module>../../bar</module>
> </modules>
> {code}
> Since the reactor plugin currently works by using "mvn --reactor", which only accepts subdirectories, it will silently fail to run these sibling modules.
> Ultimately we should fix this by using the new command line switches available in 2.1. http://docs.codehaus.org/display/MAVEN/Make+Like+Reactor+Mode  In the meantime, we'll have to live with it.  (Possibly include a warning? error?)

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