You can always wrap certain sets of dependencies up in another POM with 'pom' packaging type to keep the dependencies aspect of your pom isolated from whatever else you're having it do.
One thing I wish the pom had was a way to perform composition from common components instead of having to use inheritance. Rigid inheritance hierarchies are more difficult to maintain than delegation IMHO. For example, let's say I want a lot of my modules to use certain settings for the maven-compiler-plugin. I could just wrap those settings into a pom and inherit from it, but then if there are other common settings i want to isolate I have to put them in the same pom, or have the compiler pom inherit from the source pom or vice-versa. Perhaps I've missed something but I can't find a way to perform this sort of 'composition' as Michael has proposed within maven. Please let me know what I'm missing ! Kallin Nagelberg Consulting Architect On Dec 5, 2007 4:02 PM, Michael McCallum <[EMAIL PROTECTED]> wrote: > refactoring, composition, encasulation, aggregation standard techniques > for > making complex systems easier to understand... > > On Thu, 06 Dec 2007 09:42:49 Marco Mistroni wrote: > > hi all, > > just a quick question to see best practices with maven projects..... > > i have a pom which contains lot of dependencies... so my pom end up > being > > huge.. > > i was wondering if there is a smart way to declare them so that i don' > t > > end up with a 300 lines pom...... > > > > again, it's not a real problem, i was wondering how peoples on the list > > were dealing with it.. > > > > regards > > marco > > > > -- > Michael McCallum > Enterprise Engineer > mailto:[EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
