What is the advantage of splitting aggregator and parent projects?

Question

I read that it would be nice to separate the aggregator project (the one with all module declarations) from the parent / dependent project (with all common or shared dependencies). So the parent project is not the one you use for the full build.

Why is this?

Answer 1

Aggregator projects usually somehow package all dependent projects (for example, as a JAEE or WAR archive, or as a distribution ZIP address), which requires that all dependent projects be created first.

However, the parent POM must be created before the child objects are created.

, :

, .

, POM , . - , . Maven pom , , .

Answer 2

, (, , , ..). Maven , POM , .

( , , ). , , .

Maven, . .