Continuum

Refactoring of "Add Projects" feature

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Won't Fix
  • Affects Version/s: None
  • Fix Version/s: None
  • Component/s: Core system, Web interface
  • Labels:
    None
  • Complexity:
    Intermediate
  • Number of attachments :
    0

Description

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).

Issue Links

This issue relates to:
CONTINUUM-924 Add ability to edit group Major Closed

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Emmanuel Venisse added a comment -

we'd can add a little workflow with multiple screens when user would can customize some informations like group, notifiers, build definitions, scm username/password, authorization on this project

Show
Emmanuel Venisse added a comment - we'd can add a little workflow with multiple screens when user would can customize some informations like group, notifiers, build definitions, scm username/password, authorization on this project
Hide
Permalink
Christian Gruber added a comment -

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.

Show
Christian Gruber added a comment - 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.
Hide
Permalink
David Roussel added a comment -

I like the way in 1.0.3 it auto detects everything when adding a new project. Very impressive the first time you do it. but later you wish it confirmed the details before it actually did anything.

> have the checkout in the normal layout instead of isolated directories

This makes sense to me, since I'm using clearcase, and each module creates the same clearcase snapshot view, and hence the same data is repeated multiple times. Hence in 1.0.3 it's better to have one big project, when using clearcase.

Show
David Roussel added a comment - I like the way in 1.0.3 it auto detects everything when adding a new project. Very impressive the first time you do it. but later you wish it confirmed the details before it actually did anything. > have the checkout in the normal layout instead of isolated directories This makes sense to me, since I'm using clearcase, and each module creates the same clearcase snapshot view, and hence the same data is repeated multiple times. Hence in 1.0.3 it's better to have one big project, when using clearcase.
Hide
Permalink
Carlos Sanchez added a comment -

It needs a deep refactor because although we made great progress in identifying the problems and show them to the user in a friendly way, there are still some holes and duplicated code. For instance is a big problem to show errors from children pom urls when adding a multiproject

Show
Carlos Sanchez added a comment - It needs a deep refactor because although we made great progress in identifying the problems and show them to the user in a friendly way, there are still some holes and duplicated code. For instance is a big problem to show errors from children pom urls when adding a multiproject
Hide
Permalink
Jesse McConnell added a comment -

this is related to 924 and some discussion on the dev list...I'll link in nabble later

Show
Jesse McConnell added a comment - this is related to 924 and some discussion on the dev list...I'll link in nabble later
Hide
Permalink
Brett Porter added a comment -

I think this has been addressed by other issues over time

Show
Brett Porter added a comment - I think this has been addressed by other issues over time

People

Vote (4)
Watch (3)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.