Related to this proposal : http://docs.codehaus.org/display/MAVENUSER/Optional+support+for+splitting+up+pom.xml+in+multiple+files
I known it would allow us to create POMs that are no longer self contained but maintaining huge parent pom is a mess.
When you have dependencyManagement + pluginManagement + build + reporting ... fully configured, parent pom is really hard to maintain.
The solution we have, is to create an artificial hierarchy to split the pom
- common-dependencyManagement (with maybe pluginManagement too)
So, in this case, the fact is we already split the pom to be able to maintain it.
Perhaps you could allow pom splitting only for project of 'pom' packaging type ....