maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Seidel (JIRA)" <>
Subject [jira] Commented: (CONTINUUM-1009) When using sub project, continnum tries to check out non-existent directory
Date Sat, 03 Feb 2007 21:59:44 GMT


Stefan Seidel commented on CONTINUUM-1009:

Please correct me if I'm wrong, but IMHO this is correct Maven 2 behaviour. The SCM url defined
in the parent pom.xml sets the root path for the SCM and the subsequent paths are determined
by appending the artifactId of the subprojects. Or rather, the SCM (and also site) URLs of
the child projects are calculated by appending the artifactId to the parent's URLs. As your
artifactId of the module "plugin" is "daemon-plugin", Maven will correctly create the child
SCM URL In order to
have Continuum (and Maven) use the correct SCM URL for checkout, name the artifactId according
to the directory name, or put an extra SCM URL (<scm><connection>...</connection></scm>)
in the child's pom.xml

> When using sub project, continnum tries to check out non-existent directory
> ---------------------------------------------------------------------------
>                 Key: CONTINUUM-1009
>                 URL:
>             Project: Continuum
>          Issue Type: Bug
>            Reporter: Emmanuel L├ęcharny
>            Priority: Blocker
>         Attachments: error.txt
> I have a top level pom.xml and two subproject :
> daemon 
>   +--> bootstrappers
>   +--> plugin
> when loding the top level project into continuum, the server first check out all the
files (which is correct), but then tries to 'svn co' the sub-projects too (hich obviously
is useless, as the files have already been downloaded), but much worse, it tries by appending
the top level directory name :
> Executing: svn --non-interactive checkout
> the real directory name is plugin, not daemon-plugin.
> We could rename the directory to reflect the continuum behaviour, but as we have 3 levels
of projects, the third level will have quite a looooooog name (like apacheDS-daemon-bootstrappers
> Attached, the execution trace.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message