Good day to you, Emmanuel,
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.