You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@continuum.apache.org by "Lucien Weller (JIRA)" <ji...@codehaus.org> on 2008/04/24 12:29:46 UTC
[jira] Created: (CONTINUUM-1740) Problems with working directory
and maven2 multiprojects
Problems with working directory and maven2 multiprojects
--------------------------------------------------------
Key: CONTINUUM-1740
URL: http://jira.codehaus.org/browse/CONTINUUM-1740
Project: Continuum
Issue Type: Bug
Affects Versions: 1.1
Reporter: Lucien Weller
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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (CONTINUUM-1740) Problems with working directory
and maven2 multiprojects
Posted by "Wendy Smoak (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wendy Smoak updated CONTINUUM-1740:
-----------------------------------
Fix Version/s: Reviewed
When adding a project, you can now select "For multi-module project, load only root as recursive build". This will add a single project that builds 'from the top' recursively, rather than adding all the modules separately.
I think there are some changes in a branch that might help also, if they get merged. Possibly http://svn.apache.org/repos/asf/continuum/branches/continuum-flat-multi-module/
> Problems with working directory and maven2 multiprojects
> --------------------------------------------------------
>
> Key: CONTINUUM-1740
> URL: http://jira.codehaus.org/browse/CONTINUUM-1740
> Project: Continuum
> Issue Type: Bug
> Affects Versions: 1.1
> Reporter: Lucien Weller
> Fix For: Reviewed
>
> 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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (CONTINUUM-1740) Problems with working directory
and maven2 multiprojects
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated CONTINUUM-1740:
------------------------------------
Fix Version/s: 1.3
we're working towards this at the moment
> Problems with working directory and maven2 multiprojects
> --------------------------------------------------------
>
> Key: CONTINUUM-1740
> URL: http://jira.codehaus.org/browse/CONTINUUM-1740
> Project: Continuum
> Issue Type: Bug
> Affects Versions: 1.1
> Reporter: Lucien Weller
> Fix For: 1.3
>
> 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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CONTINUUM-1740) Problems with working directory
and maven2 multiprojects
Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=221899#action_221899 ]
Maria Odea Ching commented on CONTINUUM-1740:
---------------------------------------------
I already the flat multi-module project support branch to trunk in [-r946548|http://svn.apache.org/viewvc?revision=946548&view=revision]. 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: http://jira.codehaus.org/browse/CONTINUUM-1740
> Project: Continuum
> Issue Type: Bug
> Affects Versions: 1.1
> Reporter: Lucien Weller
> Fix For: Backlog
>
> 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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (CONTINUUM-1740) Problems with working directory and maven2
multiprojects
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ 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