[
http://jira.codehaus.org/browse/CONTINUUM-1009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_86748
]
Wendy Smoak commented on CONTINUUM-1009:
----------------------------------------
Either the artifactId must match the directory name, or you'll need to add a
<scm> element to tell Maven what url to use.
I'm not sure what you mean by '_' representing the path separator, though.
> When using sub project, continnum tries to check out non-existent directory
> ---------------------------------------------------------------------------
>
> Key: CONTINUUM-1009
> URL: http://jira.codehaus.org/browse/CONTINUUM-1009
> 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
> http://svn.apache.org/repos/asf/directory/trunks/daemon/daemon-plugin 18
>
>
> ^^^^^^^^^^^^^^
> 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:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
