Thanks Wayne for the suggestion. Yes, my parent is only a pom, interited by the module poms.
I have considered refactoring into a separate module for the site generation (a "logical parent", but technically a sibling to the modules that it is supposed to aggregate information from), just to get the ordering right. The problem however is that the approach to site report aggregation that I plan to use (copied from the javadoc and jxr plugin approach to aggregation) depends on the ability to get hold of the MavenProject objects for the modules (in order to fetch module specific settings). So I seem to be caught in a catch 22? /Bjorn > -----Original Message----- > From: Wayne Fay [mailto:[EMAIL PROTECTED] > Sent: den 2 juni 2006 00:12 > To: Maven Users List > Subject: Re: Change build order for multi-module build > > Does your parent actually contain code? Or only a pom which is > inherited by the module poms with the <parent> tag? > > If it has code, I'd restructure to put that code in another module > subdirectory, add proper dependencies in that new module's pom, and > allow Maven to figure out the proper build order etc with regular > dependency resolution. > > Can't guarantee it will fix things but I'd try that first. > > Wayne > > On 6/1/06, Björn Beskow <[EMAIL PROTECTED]> wrote: > > Hi > > > > > > > > I'm working on enhancing the Cobertura plugin to aggregate coverage > results > > when generating a report in a multi-module setting. In order to be able > to > > aggregate coverage results from the separate sub-modules, I would need > the > > sub-modules to be processed before the parent module. But it seems the > > parent project is always processed first. Does anyone know if there is a > way > > to control/change that ordering? > > > > > > > > For example, with the following structure > > > > > > > > parent > > > > |- module1 > > > > |- module2 > > > > > > > > when running 'mvn site' in the parent project, the parent will be > processed > > first, followed by module1 and module2. > > > > > > > > Any help greatly appreciated! > > > > > > > > /Björn > > > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
