> From: Vincent Massol [mailto:[EMAIL PROTECTED] > Sent: Saturday, April 16, 2005 4:07 PM > To: 'Maven Developers List' > Subject: RE: Maven 2 directory structure for Multiple Modules > configurable?
[snip] > It's actually there... (unless I've misunderstood what you meant :-)). Aahhh I see it now ;-) > Personally I still use a single Eclipse project for the > master project + all > subprojects. That's until I find a better solution... Yes exactly this is the problem in big projects. I have a multi-project build with more than 50 ejbs and 3 different developers. I use binary dependency builds with snapshots. This makes building only of the core or only parts of the modules very fast. Each ejb, jar, war.... has its own maven project and is part of the multi-project build. When I now check out the complete trunk in the new Maven 2 layout I have all ejbs (sub projects/modules) in one directory and when I start the multi-project build all ejbs are generated with e.g. xdoclet. This takes a long time and no advantage of the binary dependency build is available any longer. The solution is now to delete all ejbs I do not need to develop only for example a few modules. But this is not a fine solution to tell your developers please check out the trunk and after this you're allowed to delete this and this and..... It's nicer to say check out this core projects and then the module you want to work with. After a checkout from a project I use in Maven 1 the maven-eclipse-plugin to generate .classpath and .project. Is this working with the new directory structure too? I hope my bad English can explain my prob clear enough?! yo --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
