[
https://jira.codehaus.org/browse/CONTINUUM-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter closed CONTINUUM-1740.
-----------------------------------
Resolution: Incomplete
Fix Version/s: (was: Backlog)
Assignee: Brett Porter
Closing based on Deng's comment.
> Problems with working directory and maven2 multiprojects
> --------------------------------------------------------
>
> Key: CONTINUUM-1740
> URL: https://jira.codehaus.org/browse/CONTINUUM-1740
> Project: Continuum
> Issue Type: Bug
> Affects Versions: 1.1
> Reporter: Lucien Weller
> Assignee: Brett Porter
> Attachments: DefaultWorkingDirectoryService.java
>
>
> 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, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
