[ http://jira.codehaus.org/browse/CONTINUUM-588?page=comments#action_69837 
] 

Florian Kolbe commented on CONTINUUM-588:
-----------------------------------------

*Boils down to this*
Yes its also in 1.0.3.
The bug is as simple as this:
if the scm-URL has a CVS module 'a/b/c', continuum will do a "cvs co a" though 
it should do a "cvs co a/b/c".

*As a side note*
This constellation should actually happen quite often, e.g. we have a 
maven2-based j2ee project with a 'root' project and sub-modules for each layer, 
e.g.
jar, ejb, ear, war...

So a workaround for us would be (havent tried this yet):
we cannot use the inheritance of the scm-url through the parent-pom, but we 
must explicitely set the scm-url in each
sub-module, using a 'logical' CVS module name that we have to manage in 
CVS/modules (e.g. module "projectname-war" maps to "projectname/war").
So that contimuum wont encounter nested module paths.


> cvs checkout does not honor sub-directories
> -------------------------------------------
>
>          Key: CONTINUUM-588
>          URL: http://jira.codehaus.org/browse/CONTINUUM-588
>      Project: Continuum
>         Type: Bug

>   Components: SCM
>     Versions: 1.0.2
>  Environment: linux, cvs, continuum 1.0.2, maven1 project
>     Reporter: Aaron Smuts

>
>
> I have multiple projects in the same cvs module and I want to build them as 
> separate projects.  
> If my scm usrl has a subdirectory, the checkout brings in the entire module 
> regardless.   The end of my scm string looks like this  
> ":my-module/my-project".  Continuum checks out my-module instead of 
> my-module/my-project
> To get around this I set the address of my project.xml as 
> "my-module/project.xml".  It was able ti find it, but there were other 
> problems.  The working directory was now at the root of the module and not 
> the project, so tests that needed files in target/some-directory and log4j 
> with a relative path defined to the log directory failed as well . . . .

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

Reply via email to