You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Ivan Dubrov <du...@gmail.com> on 2012/11/16 17:56:55 UTC

Aggregate modules and parallel builds

Hi,

During non-parallel build aggregate POMs are built last provided there is
no parent-child relationships between it and its submodules (correct me if
I am wrong).

Is that preserved during parallel builds? Can I assume that root POM is
built after all its submodules are built? According to the build logs, it
seems like the answer is "no", but maybe I am missing something.

If answer is "no", how can I ensure that aggregate POM is built last? For
example, I want to run assembly plugin after all submodules are built (in
parallel build)? Of course, I can run separate "mvn -N assembly:assembly"
command to assemble built stuff, but is there a way to do that during
regular build?
I don't want to specify dependencies explicitly since it could be
error-prone (submodules dependencies could change, for example).

Can we have this convention back? Make
org.apache.maven.project.ProjectsSorter to add "weak" dependencies from
aggregate module to all its children?

-- 
WBR,
Ivan Dubrov