RE: Maven 2 directory structure for Multiple Modules configurable?
Hi Joachim, Joachim Schreiber wrote on Saturday, April 16, 2005 6:28 PM: [snip] 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?! You may tell your developers to work with a local build.properties file in the multiproject root, that contains the maven.multiproject.include (or maven.multiproject.include) property, e.g. maven.multiproject.include=\ ejb1/project.xml, \ ejb2/project.xml, \ webapp1\project.xml ... you get the idea. The value just overrides the one found in project.properties. If they check out individual subprojects only, you might even generate that entry for all locally available subprojects with a script. This way everyone can have an individual multiproject builds. Just ensure, that build.properties is excluded in the .cvsignore (this file should never be checked in anyway). - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven 2 directory structure for Multiple Modules configurable?
Joachim Schreiber wrote: [...] Now I read in the Getting Started section of the new Maven 2 documentation in Subsection Multiple Modules the new plans for creating multiple modules. I want to ask, is the new directory structure configurable? +- pom.xml +- my-app | +- pom.xml +- my-webapp | +- pom.xml I saw this new structure in Vincent Massol's ppt presentations and examples and now in Maven 2 (but not in Cargo ;-). I'm interested because the pitfall with Eclipse is that this kind of directory structure is not supported. AFAIK the only limitation which exists in eclipse is that project directories cannot overlap. So you should be able to import to eclipse all projects, which contain java sources and are leaves in the directory tree. So in you case you can create eclipse projects for my-app and my-webapp In more complex case +- pom.xml +- my-app | +- pom.xml +- my-webapp | +- pom.xml +- subprojects +- pom.xml +-sub1 +- pom.xml +-sub2 +- pom.xml you can create eclipse projects for my-app, my-webapp sub1 and sub2. But there are other tools which may require (or recommend) other directory layout. For example subversion. I don't know if recommended subversion layout which is already quite frequently used is already supported in m2: maven-plugins/ |_ plugin1/ |_ trunk/ |_ branches/ |_ tags/ |_ pluginN/ |_ trunk/ |_ branches/ |_ tags/ and how to use it with help of modules section in pom. Is something like this going to be supported: modules moduleplugin1/trunk/module ... modulepluginK/tags/3.2/module ... modulepluginN/trunk/module /modules or users will be forced to use svn:externals in such cases (or something else)? Michal Nie dzwon do Londynu... zanim nie sprawdzisz HALO.interia.pl Tutaj: http://link.interia.pl/f1870 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Maven 2 directory structure for Multiple Modules configurable?
From: Michal Maczka [mailto:[EMAIL PROTECTED] AFAIK the only limitation which exists in eclipse is that project directories cannot overlap. Yes So you should be able to import to eclipse all projects, which contain java sources and are leaves in the directory tree. So in you case you can create eclipse projects for my-app and my- webapp Ok I do this and... eclipse_workspcae +- my-app | +- pom.xml +- my-webapp | +- pom.xml ...I have no root project for my root pom.xml because the root is the workspace and there is no possibility to check out something from inside eclipse in the workspace. Do I misunderstand? yo - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven 2 directory structure for Multiple Modules configurable?
Joachim Schreiber wrote: From: Michal Maczka [mailto:[EMAIL PROTECTED] AFAIK the only limitation which exists in eclipse is that project directories cannot overlap. Yes So you should be able to import to eclipse all projects, which contain java sources and are leaves in the directory tree. So in you case you can create eclipse projects for my-app and my- webapp Ok I do this and... eclipse_workspcae +- my-app | +- pom.xml +- my-webapp | +- pom.xml ...I have no root project for my root pom.xml because the root is the workspace and there is no possibility to check out something from inside eclipse in the workspace. Do I misunderstand? Last time I did two ~ months ago as I am using different ide more often so sorry if my memory is playing tricks: I used import feature to import existing projects into the workspace. So afaik you can keep your projects where ever you want and just virtually add them to any workspace. I used one of the milestones builds of eclipse 3.1. I don't know if this is something new for eclipse 3.1 or if it works also for 3.0 michal -- Startuj z INTERIA.PL! http://link.interia.pl/f186c - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Maven 2 directory structure for Multiple Modules configurable?
-Original Message- From: Joachim Schreiber [mailto:[EMAIL PROTECTED] Sent: samedi 16 avril 2005 12:27 To: dev@maven.apache.org Subject: Maven 2 directory structure for Multiple Modules configurable? [snip] +- pom.xml +- my-app | +- pom.xml +- my-webapp | +- pom.xml I saw this new structure in Vincent Massol's ppt presentations and examples and now in Maven 2 (but not in Cargo ;-). It's actually there... (unless I've misunderstood what you meant :-)). BTW I've also committed the maven2 pom.xml in Cargo about a week ago (with more modifications done this morning - I'm slowly creating a m2 build but m2 is still missing some plugins like checkstyle, ear, reports, etc). [snip] Personally I still use a single Eclipse project for the master project + all subprojects. That's until I find a better solution... -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Maven 2 directory structure for Multiple Modules configurable?
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]
Re: Maven 2 directory structure for Multiple Modules configurable?
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'm sure it should all work the same. I know the m2 eclipse plugin is not yet up to the same functionality as the m1 version. But you should be able to generate .project .classpath for each project and add them as desired to the workspace. Note that the directory layout is just a recommendation, there is nothing that m2 requires about it. - Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
