[ http://jira.codehaus.org/browse/CONTINUUM-741?page=comments#action_68510 ]
Christian Gruber commented on CONTINUUM-741: -------------------------------------------- The other important thing (and I'm not sure if that needs to be stated here or elsewhere), is that if you have a parent pom.xml which has several modules, and you import, you get many projects... but if you later add a new module, or remove a module, those modules are not added nor removed from continuum. THAT would be the single best feature around project and group management I can imagine. Very tricky owing to the scm urls, but I suspect that using hte module name (whether "foo" or "../foo") attached to the scm url, it could be managed. > Refactoring of "Add Projects" feature > ------------------------------------- > > Key: CONTINUUM-741 > URL: http://jira.codehaus.org/browse/CONTINUUM-741 > Project: Continuum > Type: Improvement > Components: Web interface, Core system > Reporter: Emmanuel Venisse > Fix For: 1.1 > > > evenisse: customization of the add project feature. In this part, I think to > add a multi-project as a multiple projects or as a single project, scm > connection string to use, add with a scm url, add all modules by a scm > connection instead of an url contruction based on project url provided in the > add screen > brett: Absolutely. We should talk through this one a bit more, as maybe the > solution is to have it better understand module relationships. This also > relates to something I'd like to see happen where we have the checkout in the > normal layout instead of isolated directories (to avoid checking out the > modules twice - once in the parent and once for each module). -- 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
