We started using multi-module project for the first time and notice strange behaviour. We hope that some experienced user can tell us how to proceed.
There is one multi-module project where module 1 is dependend on module 2. Module 1 uses assembly plugin in the package phase to produce the final artifact (zip file). Modul 2 uses dependency plugin in the generate-source phase to unpack that artifact (zip file). When we execute module 1 only (maven install) and after that module 2 (maven compile) all works well. When we execute the multi-module parent (maven compile) then it fails, because the zip will not get bundled then obviously, so module 2 cannot find it. So how to tell maven that in a multi-module project, we want module 1 to run up to install but module 2 to run up to compile only? Or is it wanted by desing that in a multi-module project we always must run to install phase to be sure that module 1 is done before module 2 starts? We hoped that a multi-module project would solve this automatically, i. e. mvn compile on the parent shall notice that it must actuall do install but not compile on module 1 as it is a dependency to module 2...! -- View this message in context: http://maven.40175.n5.nabble.com/multi-module-phases-sequence-tp5789365.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]
