continuum-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lucien Weller (JIRA)" <>
Subject [jira] Created: (CONTINUUM-1740) Problems with working directory and maven2 multiprojects
Date Thu, 24 Apr 2008 10:29:46 GMT
Problems with working directory and maven2 multiprojects

                 Key: CONTINUUM-1740
             Project: Continuum
          Issue Type: Bug
    Affects Versions: 1.1
            Reporter: Lucien Weller

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 rules:
* 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