continuum-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Emmanuel Venisse <emman...@venisse.net>
Subject Re: Problem checkout cvs moduleAlias with continuum
Date Thu, 09 Mar 2006 14:01:00 GMT
I'm not sure if it will work, but you can try this :

modulealias -a module1 module2
parentPom module3 pom.xml
projectalias -a &parentPom &modulealias

Test it before with cvs command line before to try it in continuum

Emmanuel

Gautham Pamu a écrit :
> Hi Everyone,
> 
> I have a problem checkout project from our CVS tree with module alias. I
> have a following CVS tree under the CVSROOT.
> 
> Module1
>    ... pom.xml
>       submoduleA1
>           -pom.xml
>       submoduleA2
>           -pom.xml
> Module2
>    ... pom.xml
>       submoduleB1
>           -pom.xml
>       submoduleB2
>           -pom.xml
> ModuleAlias -a Module1 Module2
> 
> and I created a module alias which points to Module1 and Module2. I heard
> that we cannot checkin a pom.xml file at toplevel of the CVSROOT.  One user
> on maven
> user group suggested, to create a new module and pom.xml file in it and
> create symbolic links from it to these modules or create new module and
> refactor the modules into it.
> Since we dont have access to the cvs server, so we cannot create those
> links. If we take the second approach, it requires
> changes to our CVS tree, which we are trying to avoid, if possible.
> 
> So we are looking for other alternate workarounds..
> 
> So we defined a module alias to other directory and we wanted continuum to
> checkout the module alias and have a script which copies the pom.xml file to
> the workinging directory.
> But when continuum checkout the projects with the alias, it copies the
> subprojects in the Module1 to working directory instead of creating the
> subprojects under the Module direcotory.
> So when it tries to checkout subprojects from the second module, it fails.
> 
> INFO   | jvm 1    | 2006/03/07 15:35:23 | 2006-03-07 15:35:23,025 [Thread-3]
> WARN  ContinuumScm                   - Error while checking out the code for
> project: 'Master POM File projectName', id: '1' to '/usr/local/continuum-
> 1.0.2/bin/linux/../../apps/continuum/working-directory/1'.
> INFO   | jvm 1    | 2006/03/07 15:35:23 | 2006-03-07 15:35:23,026 [Thread-3]
> WARN  ContinuumScm                   - Command output: cvs checkout:
> existing repository /cvsroot/projectName/Module1 does not match
> /cvsroot/projectName/Module2
> INFO   | jvm 1    | 2006/03/07 15:35:23 | cvs checkout: ignoring module
> Module2
> 
> After continuum checkout the modules from cvs using module alias, Is it
> possible to copy this pom.xml to continuum working output/build output
> directories
> so that before maven starts to build the code, it has the pom.xml at the
> toplevel which defines the modules etc.
> 
> The ID number in working/build output directory does it change for every
> build or it is constant for a project.
> 
> --
> -Gautham Pamu
> 


Mime
View raw message