On Dec 11, 2007 10:12 AM, Jeff MAURY <[EMAIL PROTECTED]> wrote: > Hello, > > I have the following problem: > A multi module POM (called M) has tow modules A and B. > If I run Maven on M, then the execution order is A,B and M. > > Now, let assume that M is the parent of A and B. > The execution order is changed to M,A and B > This causes me some trouble because I want to run plugins when M is builded > that need to get stuff from A and B in the local repository. > Another case is that you want to generated Javadoc with M and A or B cause > generation of source files : if M is executed before A and B, then the > Javadoc may be incomplete !!! > > Does everyone has experienced the same problem and is it a Maven bug or a > Maven feature ? > > Thanks > Jeff
By making the parent module also contain build operations that depend on the children, you basically created some sort of dependencies cycle. Move the files to build (probably all src/main src/test src/it...) from M into a new sub-module (called C) and make C depend on A and B. Keep your parent POM a simple 'aggregator' that doesn't contain anything to build and just reference all the sub-modules. Cheers, Jerome --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
