Hello Guillaume, I must say I've tried both with almost equal success, the one positive advantage of the hierarchical option is that it allows the option of having multiple depths of hierarchy without the quick growth of the number of folders on a level. It also helps organize the structure when there's a large number of sub-projects.
My 2 cents :-D w On Fri, Nov 21, 2008 at 8:44 PM, Jeudy, Guillaume <[EMAIL PROTECTED]>wrote: > Hi Maven gurus, > > I would like to know what is the best recommended way of definining maven > multi-module projects? > > Is it the hierarchical ? > > parent/pom.xml > parent/childA/pom.xml > parent/childB/pom.xml > > or flat-structure ? > > parent/pom.xml > childA/pom.xml > childB/pom.xml > > > I'm using eclipseIDE with m2eclipse and hierarchical multi-module structure > and the maven release plugin to manage my release cycle. My setup works > reasonably well but I have seen others using the flat-structure. > > Can someone tell me what are the pros and cons of both approaches? I'm not > sure which one is best. > > Thanks, > -Guillaume > > > > ____________________________________________________________________________________________________ > This electronic mail (including any attachments) may contain information > that is privileged, confidential, and/or otherwise protected from disclosure > to anyone other than its intended recipient(s). Any dissemination or use of > this electronic email or its contents (including any attachments) by persons > other than the intended recipient(s) is strictly prohibited. If you have > received this message in error, please notify us immediately by reply email > so that we may correct our internal records. Please then delete the original > message (including any attachments) in its entirety. Thank you. >
