continuum-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maria Odea Ching (JIRA)" <>
Subject [jira] Commented: (CONTINUUM-1740) Problems with working directory and maven2 multiprojects
Date Thu, 20 May 2010 09:38:12 GMT


Maria Odea Ching commented on CONTINUUM-1740:

I already the flat multi-module project support branch to trunk in [-r946548|].
It's now possible to checkout a project into a single directory with each module still treated
as separate projects in Continuum.

Is it safe to close this now? 

> Problems with working directory and maven2 multiprojects
> --------------------------------------------------------
>                 Key: CONTINUUM-1740
>                 URL:
>             Project: Continuum
>          Issue Type: Bug
>    Affects Versions: 1.1
>            Reporter: Lucien Weller
>             Fix For: Backlog
>         Attachments:
> I experieced problems with maven2 multiprojects in continuum, hen modules are referencing
each other relatvely. So I made the following change to class DefaultWorkingDirectoryService
of project continuum-commons:
>         if ( project.getWorkingDirectory() == null || project.getWorkingDirectory().equals(Integer.toString(
project.getId() )))
>         {
>             // project.setWorkingDirectory( Integer.toString( project.getId() ) );
>             project.setWorkingDirectory(project.getProjectGroup().getName() + '/' + project.getArtifactId());
>         }
> This assumes that every project group in a continuum installation has a unique name and
that an artifact is only once in a project group. I think this is realistic.
> But in any case it would be nice to change working dir handling to meet the following
> * all modules of a multoproject are located in the same working directory
> * the directories of the modules are named after their artifactId
> So the working dir structure used by continuum is the same as it would be normally for
a deveopper.

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