Okay... So let's write a spec :-p --jason
-----Original Message----- From: Jason van Zyl <[EMAIL PROTECTED]> Date: Sat, 28 Jul 2007 18:28:31 To:"Maven Developers List" <[email protected]> Subject: Re: Importing poms, as well as extending them On 28 Jul 07, at 5:41 PM 28 Jul 07, Jason Dillon wrote: > > Heh, ya, no kidding. At this point I'm just trying to start a > dialog with the community to get feedback.... on the concept, > potential impacts, potential roadbumps, as well as maybe a hint or > two of like "if you wanted to try, maybe you could look at X.class > and see how parent merging goes, blah, blah, blah" ;-) > The key that's missing is no spec on inheritance/aggregation of each element given the influence of profiles, settings and interpolation. Once that was sorted out then importing a chunk of into a given POM should not change the spec'd behaviour. But implementing that mechanism without this spec would only cause more grief IMO. > Cheers, > > --jason > > > >>> 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] >>> >> >> Thanks, >> >> Jason >> >> ---------------------------------------------------------- >> Jason van Zyl >> Founder and PMC Chair, Apache Maven >> jason at sonatype dot com >> ---------------------------------------------------------- >> >> >> >> >> --------------------------------------------------------------------- >> 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] > Thanks, Jason ---------------------------------------------------------- Jason van Zyl Founder and PMC Chair, Apache Maven jason at sonatype dot com ---------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
