[
http://jira.codehaus.org/browse/MNG-3377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=176994#action_176994
]
Jörg Hohwiller commented on MNG-3377:
-------------------------------------
This is definitely no duplicate.
My suggestion was to put all projects starting from toplevel-pom into the so
called reactor but not in order to execute them but just to have them available
for the plugins. I can NOT easily tell if this fits into mavens architecture at
all after I understood what has been done in MNG-2576.
However this is more how I am working. I "cd" to some module and maybe look at
target/surefire-report or edit pom.xml.
Then I would not typically "cd" back to toplevel and then do some strange mvn
command with the path to where I have been before as argument but rather call
mvn in the place where I am in order to build that module.
> Build reactor from toplevel pom
> -------------------------------
>
> Key: MNG-3377
> URL: http://jira.codehaus.org/browse/MNG-3377
> Project: Maven 2
> Issue Type: Improvement
> Reporter: Jörg Hohwiller
>
> The following is all about multi-project environments.
> For many maven calls the result differs if you perform you mvn command on the
> toplevel project
> or in a specific module. In the latter case the related modules of the
> projects are not included in the reactor
> causing the result to be invalid or the build to fail.
> There should be a way that I can call maven within a particular module
> causing the reactor
> to be build from the toplevel pom while walking the relativePath (defaults to
> ../pom.xml) upwards
> until a pom is reached, that has no parent. From that pom the reactor should
> be build,
> while the actual build should work on the module where maven was invoked.
> A typical example use-case would be the command "mvn eclipse:eclipse".
> Right now it does not create project-internal dependencies if it is called
> within the module. This is especially nasty when you have a local sandbox
> module that should not (yet) be committed. Then you always need to add it
> as extra module to your parent pom, call eclipse:eclipse and then revert the
> changed pom.
> Additional use-cases are that you want to build a specific module rather than
> the entire project. Right now you need to enter the module, give "mvn
> install" a try.
> If it fails, you will see which dependency is missing. Then you go there
> before
> and try "mvn install" there. This process is iterated until the first "mvn
> install" completes.
> This is very inconvenient. However fixing such problems as well would
> cause that not only the modules are added to the reactor but that the actual
> mvn call
> is also applied to the dependend modules that are in the reactor.
> This specific issue might need some extra discussion...
> For reasons of compatibility the suggested improvement could/should be
> activated by a specific commandline option (somehow the opposite of "-N").
> A suggestion would be "-R" for reactor and recursive.
--
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
