Thanks for verifying that my expectations where correct.
I have seen this problem in mvn 2.0.8. Make a standalone test case may be hard but I will try and do it if I can find the time. John Stoneham wrote: > > On Sat, Dec 20, 2008 at 4:57 PM, Farrukh Najmi > <[email protected]> wrote: >> >> I have a top level of multimodule project that contains multiple sub >> modules. >> If I do the following steps in the top level project: >> >> mvn clean >> mvn install >> >> I get build failure because what mvn seems to do is to first run compile >> goal on all the sub-modules before running install goal on all the >> sub-modules. The problem is that some sub-modules depend upon other >> sub-modules and I have to manually run "mvn install" on thos modules >> first >> in order for my tope level "mvn install" to succeed. Is there a more >> elegant >> way to address my problem? > > If you're in a multimodule project, the installation part shouldn't > even matter; if the projects are linked via actual dependencies, the > build order will be sorted appropriately so that leaf dependencies are > built last, and the reactor will compile each project against the > other's compiled artifacts. Also, on a multi-module mvn install, it > will go all the way through to installation prior to moving on to the > next module. > > In essence I would say that you're typing the right commands, but what > you're reporting isn't consistent with how Maven works. Can you > provide a log or other information? > > - John > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > > -- View this message in context: http://www.nabble.com/mvn-install-on-a-top-level-of-multimodule-project-tp21109766p21115453.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
