Community
Participate
Working Groups
For working with EMF/GMF/EMFT/UML2/XSD as CVS projects I need to check out more than 160 projects. So I thought this ability to import and export a team project set would be very useful to avoid having to select 160 projects each time I start a new workbench. Normally, in order to provide a self-hosting bootstrapped environment, when I check out the CVS projects, I locate them in the actual plugins directory of the Eclipse I am running. The Check Out As dialog lets me specify where all the projects go, so that makes me happy. After everything is checked out, I can exit Eclipse, run a script to build the jars (or copy the bin directory to the root of the project) and then I restart Eclipse which now has all my tools working so I can use my own tools to further develop my own tools, i.e., use the generator to regenerate itself. All this works rather nicely and the ability to export and import a team project set would make my life much simpler. But it suffers from the show stopping problem that you cannot specify the location where the projects should go during the import step. So the feature request it so provide the same "Select project location" page for the "Import Team Project Set" wizard and appears in the "Check Out As" wizard.
This is a good suggestion but unfortunately, we don't have time to address it in 3.3. Here's what the solution would require 1) The CVSProjectSetCapability (in the org.eclipse.team.cvs.core plug-in) would need to be modified to obtain a location from the user which would then be used as the location for all the projects that are created. 2) The above mentioned class is a core class so a prompt method would need to be added to the ProjectSetSerializationContext (from the org.eclipse.team.core plug-in). Of course, ProjectSetSerializationContext is also a core class, so we would need to add a promptForLocation that does nothing there and add the real prompt to the UIProjectSetSerializationContext (from the org.eclipse.team.ui plug-in).
Bug 107371 requests for API to specify the target directories to which the projects are checked out during an import.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
