Folks, I think this may have come up before, though I've not gone
digging in the jira or mailing list trenches for it...
I would be *really, really useful* if a pom could include other poms
into its effective pom *in addition to* the parent pom. The parent
pom and tree structure is very useful for defining projects and
scoped configuration muck for a single project, but when wanting to
share more pom elements with many projects, the inheritance model
breaks down significantly and ends up causing projects to duplicate
elements to control common build scenarios, which then causes more
maintenance... and in the end ultimately ends up in a rather big
mess :-(
I would really like to define a simple pom module, that defines some
common pom elements, maybe in a profile, maybe not. And then
configure my projects root pom (er the top-level pom that is) to
*include* the pom modules to get that poms elements overlaid into the
current effective pom. In the same way that works for the parent
really. Maybe first apply includes/imports (whatever you call them)
then parent, and then local overrides take precedence or something
like that.
Of course reference the poms to be included in the same way that the
parent is defined, yada, yada, yada.
IMO, this would be a *HUGE* benefit to the entire Maven community, as
then at this point folks can start to develop and share common build
configurations and let projects consume them easily.
It doesn't seem like rocket science... though I've not dug into the
depths of the plexus, modelo and other bits that made the pom
inheritance bits work.
Just for clarification, I'm not for tossing out the parent/child
bits, those are also important, but I think we need a kinda mixin for
pom configuration too.
Any thoughts?
--jason
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
