Community
Participate
Working Groups
Some times there arise a requirement to include two projects having the same name into workspace.(under different working sets). If we try to import that the wizard will ignore that project since there is an project already there with that name opened in the workspace. This is the scenario -> Say that we have the build system in Maven/Maven2 It has this facility to generate the eclipse projects for us. If the projects contains dozen of modules then its very easy to generate using it. So the above requirement arrives when we are working with trunk and branch of that project simultaneously. If this feature is available in eclipse it will be a vast improvement in productivity coz this will enable features like comparisons and merging them, viewing diffs etc. At least it will be ethical to inform the user that there is an project already opened with that name.
It is not possible to have two or more projects with the same name in the workspace. Even if they are in different working sets. I agree, that the import wizards UI should show all projects, those with existing names grayed and disabled. The wizard could offer to rename, overwrite this projects.
(In reply to comment #0) > Some times there arise a requirement to include two projects having the same > name into workspace.(under different working sets). If we try to import that > the wizard will ignore that project since there is an project already there > with that name opened in the workspace. > > This is the scenario -> > Say that we have the build system in Maven/Maven2 > It has this facility to generate the eclipse projects for us. If the projects > contains dozen of modules then its very easy to generate using it. So the above > requirement arrives when we are working with trunk and branch of that project > simultaneously. If this feature is available in eclipse it will be a vast > improvement in productivity coz this will enable features like comparisons and > merging them, viewing diffs etc. > > At least it will be ethical to inform the user that there is an project already > opened with that name. > Compared to the advantages that we receive with this, I still think this is a very good feature improvement that developers would love. It does not matter if eclipse change the project names (actually set of sub projects) with a suffix plus give an warning that there are already a projects under that category or we can come up with a agreed solution to this. Open to discussion.... Thanks Lahiru Sandakith
Although not quite the same thing I am going to mark this as a duplicate of Bug 173994 as the discussion of what to do in the colliding projects case is going on there. *** This bug has been marked as a duplicate of bug 173994 ***
