this is basically my goal at the moment in regards to m2 root/ root/core root/war1 - uses core, lib1 root/war2 - uses core, lib1, lib2 root/war3 root/ejb1 - uses lib1, core root/ejb2 - uses lib2, core root/lib1 root/lib2 root/ear1 - uses war1, war2, ejb1 root/ear2 - uses war3, ejb2
basically just seperate the source as much as makes sense into seperately compilable units, and then in the pom.xml for the wars, ejb, and ear just source in the dependencies that are needed in a bit of a tree. problem becomes when you have a hefty chunk of classes that are pretty entertwined, but its my feeling that adopting this kinda structure allows you to grow into a cleaner seperation of logical entities. nice thing about that is say that your team splits and each team takes control on one of those ears, it is pretty easy to setup either cvs modules or subversion to pluck those things out and share those 'subprojects' between the root projects. only issue I am running up against now is that my ears are coming out a fair amount bigger then our existing ant system...but that is actually what I'll be tackling tomorrow. my 2 cents, jesse On 7/20/05, Manny Nainu <[EMAIL PROTECTED]> wrote: > I'm curious also to know if anyone from the Maven team can comment on Ken's > project directory structure for Maven 2. We are in a similar predicament > with Maven 2 with mutiple applications with multiple EARs. There doesn't > seem to be enough depth on the > [http://maven.apache.org/reference/conventions.html] page. Any pointers > sincerely appreciated. > > > > Thanks, > Manny > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- jesse mcconnell jesseDOTmcconnellATgmailDOTcom --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
