well for the last couple of years, I have never encounterred a event/task where we, mojo developers, need to use the modules except to just enter them in the list. So what is the point to maintain the modules? even if we have them there do we want to enforce it? lean and mean is what i am after.
-D On Sat, May 3, 2008 at 8:56 AM, Benjamin Bentmann <[EMAIL PROTECTED]> wrote: > Benjamin Bentmann wrote: > > > > > > Dan Tran wrote: > > > > > also we should remove all the modules element, i dont see a need for it. > > > > > > > > > I somehow find David Jencks' proposal quite attractive: Leave the > <modules> in but move them into a profile. This way, the aggregator can be > enabled on demand. > > > > Another idea: We could have inheritance and aggregation handled completely > independently by two separate POMs: > > trunk/ > mojo-parent/ > pom.xml <-- the inheritance parent, no <modules> here > ...plugins... > pom.xml <-- the aggregator, <modules> here > > > Benjamin > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
