I ended up setting up two cvs modules to manage the migration from our ant setup to m2. Basically since we have over 4 years of history in the one project and most of the developers aren't that adventurous I have maintained out our cvs module and provide a new one that mounts the old src directory into the right spot on the new build architecture. It works like a wonder :)
since I also wanted to support the refactoring of the source as well I ended up making a mess of cvs module alias to particular packages in the main source root and just move them around accordingly in the m2 build setup...when the old setup goes away I can move the files around in the cvs respository by hand and get them into the right place...but that is still a ways out. if this is anything you are interested in, let me know and I'll steer you in the right direction. Jesse On 9/13/05, Allison, Bob <[EMAIL PROTECTED]> wrote: > > We have our entire project, including subprojects, in a single CVS module. > The directory at the top of the module contains the root POM, etc. Each > subproject is a subdirectory of that top level. > > -----Original Message----- > From: news [mailto:[EMAIL PROTECTED] On Behalf Of Nelson Arape > Sent: Tuesday, September 13, 2005 10:16 > To: [email protected] > Subject: RE: [m2] Multiproject directory organization on CVS > > > Sorry, I did not make may self clear. I don't have problems with How maven > handles subprojects, but in how organize thos projects in a CVS > repository. > > How I look, I have to options: > 1.- Make the whole project and subprojects a module in the CVS repository. > 2.- Make each subproject a distinct module in the CVS repository. > > I originally thought that 1 was the way to go, but then I haven't a place > to > store the project (root) pom.xml, src/site and src/assembly files. > > So now I think option 2 is the way to go. > > Can anyone confirm, denied or expand my assumptions > > Nelson Arape > Yann Le Du wrote: > > > Hello Nelson, > > > > --- Nelson Arape <[EMAIL PROTECTED]> a écrit : > > > >> Hello to all > >> > >> I have a multiproject directory organization as follows: > >> > >> project > >> +-core > >> +-optional-plugin1 > >> +-optional-plugin2 > >> +-optional-plugin3 > >> +-examples-files > >> > >> I originally thought that I should create all subprojects as CVS > modules, > >> but what do I do with the project pom?. > > > > So that a goal executed in project be recursively executed in > subprojects, > > you could add the following in the project pom : > > > > <modules> > > <module>core</module> > > <module>optional-plugin1</module> > > ... > > </modules> > > > >> > >> Additionally I am also planing to use the site plugin, so should i > create > >> a src/site on project or a site subproject instead? > > > > For myself, I use a src/site. This allows me to simply execute the site > > plugin in project, which recursively calls the same in subprojects. > > > > I believe the Maven dev team uses a site subproject, maybe someone can > > comment on the pros & cons ? > > > >> > >> Thanks in advance > >> Nelson Arapé > >> > >> PS: sorry for my english > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > >> For additional commands, e-mail: [EMAIL PROTECTED] > >> > >> > > > > Regards, > > Yann > > > > Yahoo! Mail - Votre e-mail personnel et gratuit qui vous suit partout ! > > Créez votre Yahoo! Mail sur http://mail.yahoo.fr > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- jesse mcconnell
