[ http://jira.codehaus.org/browse/CONTINUUM-1098?page=comments#action_83895 ] Franz Allan Valencia See commented on CONTINUUM-1098: -----------------------------------------------------
Good day to you, Emmanuel, I see. So I guess this no-duplice-project rule applies not only to the uploading of m2 project (with submodules) but to other tasks as well ( such as manually adding a project that already exists, moving to a group where that project already exists, etc). Did I get that right? Also, will this rule will apply to m1, ant, and shell project as well? And what would be the definition of a project duplicate? For M2, would it be if two projects have the same artifact key and belong to the same project group? Or will we included packaging? ..And what about for the other project types? Maybe this deserves an issue of its own :-) If so, maybe this issue can progress on its own and we'll just add the no-duplicate-project mechanism later on when its finish. WDYT? Cheers, Franz > Cannot upload a Maven 2 Project with modules > -------------------------------------------- > > Key: CONTINUUM-1098 > URL: http://jira.codehaus.org/browse/CONTINUUM-1098 > Project: Continuum > Issue Type: Improvement > Components: Core system, Web interface, Web - UI > Affects Versions: 1.1 > Environment: -r490655 > Reporter: Franz Allan Valencia See > Attachments: error logs.txt, error page.JPG > > -- 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
