Community
Participate
Working Groups
Eclipse currently only allows one project at a time to be shared (with the Project -> Share Project menu). If uploading a bunch of projects into the same repository, it would be nice to allow multiple projects to be shared at the same time without having to repeat the same wizard for each.
I agree tha this would be usefull. However, there are several complications that make this difficult: 1) It would require new API that would need to be implemented by all repository providers. A backwards compatibility story would need to be in place for those providers that only provide single project sharing (i.e. the same providers would need to appear in both the single and multi project share case or the user would be confused). 2) Multi-project sharing is fairly straight forward but can get complicated when either some of the projects already contain repository meta-information or when some of the projects being shared collide with projects that already exist in the repository. Point 2 is not that big an issue for CVS but it may be for other repository providers. Point 1 the biggest road block for me. The only backwards compatibility story I can come up with is to run the single project sharing wizard for each project being shared. This seems a bit clunky.
I agree that you'd need to have a backwards compatibility story in place to support those that don't support it. But your comment #1 (point 1) of having the backwards story being 'clunky' at having to re-run the same wizard multiple times is no different than at present; in fact, at the moment it's even worse because you must select each project individually and select 'Team -> Share Project' to bring the wizard up each time. At least having the ability to select projects and issue the command once is an improvement, even if it has to fire the single-project-wizard repeatedly. As for point 2 (or indeed, any pre-selected project that is already shared/has metadata), if the selected projects are already shared then a warning/question dialog could be proposed "Project X is already shared under Y; do you want to leave it shared/share it with a different repository". Ideally, this might happen after the repository/method has already been chosen, and filter out projects that are already shared under the same repository.
*** Bug 126339 has been marked as a duplicate of this bug. ***
Perhaps a Project Set can also be constructed on the fly when sharing a group of projects ?
From a practical point of view: I am having to recreate a Workspace after an Eclipse upgrade. Why do I have to invoke the share project command 20 times? I'm not convinced by the API problem. Surely it can be an outer loop that is independent of the underlying CM system.
comment #1 2) if the project already contains repository information, the multi-project share wizard could simply refuse to work. But having to run the wizards 100 time (I'm about to check in 100 projects) is *very* annoying. I think it's worth for me to learn the CVS command line and check the projects in using the command line. I was hoping I could avoid this....
We don't have the manpower to address this in 3.3. The case has been improved somewhat since CVS now support auto-sharing of projects that contain CVS meta-data so this is only an issue when you have multiple new projects that need to be shared.
Created attachment 61905 [details] Adds dumb outer loop for sharing multiple projects in sequence The auto-sharing on import isn't working for me. My workspace containing Eclipse from HEAD got corrupted, so I deleted the .metadata, restarted Eclipse, and imported Existing Projects Into Workspace; they didn't get auto-shared. Should I enter a bug? The attached patch takes a first stab by letting the user invoke Share Project on multiple projects and launching the wizard once for each project in sequence. In my case, I reshared each of my 102 projects, which took 102 repetitions of [right-click, "e", "s", Enter]. With the patch, I would need a few clicks to select all the projects, right-click, "e", "s", and 102 Enters; this is a slight improvement.
Let me take a stab at this, it bugs me too and I work with a repo with supports multiple project sharing in it's wizard by showing the unshared projects. It would be nice if multiselect worked as well. No promises for 3.3 (eg, no milestone set yet), but I'll try.
*** Bug 180017 has been marked as a duplicate of this bug. ***
Could we address this for 3.3 ?
Yes, I'll try.
Given that we are winding down 3.3 M7, I think we'll need to defer this until 3.4.
Created attachment 65877 [details] Adds dumb outer loop; updated to apply cleanly to HEAD 5/3/2007
Lowering priority. This is not a stop-ship problem.
*** Bug 136148 has been marked as a duplicate of this bug. ***
I have released the Team API for this to HEAD. If the target repository wizard implements or adapts to the IConfigurationWizardExtension, then this new API will be used when multiple projects are selected. If a selected wizard does not implement or adapt to the interface, a wizard page containing the selected projects is shown and individual sharing wizards can be launched from there. I have created bug 198314 against CVS to take advantage of this new API.
I find it mildly confusing that the "Cancel" button on the wizard page for sharing individual projects doesn't cancel anything. Would it be possible to disable the button?
Please raise a new bug for the issue.
