Bugzilla – Full Text Bug Listing
| Summary: | [Import/Export] Import several projects at once | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Rodrigo Peretti <rodrigo> |
| Component: | UI | Assignee: | Tod Creasey <Tod_Creasey> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P2 | CC: | bogofilter+eclipse.org, colinml1, daniel_megert, danrubel, gabriele.garuglieri, ggregory, gunnar, igor, kaj.hejer, llowry, mlq.eclipse, nick.entin, nikolaymetchev, nobody, robert.yarrow, shanec, sja.eclipse, slavescu |
| Version: | 2.0 | Keywords: | helpwanted |
| Target Milestone: | 3.1 M4 | ||
| Hardware: | PC | ||
| OS: | Windows 2000 | ||
| Whiteboard: | |||
|
Description
Rodrigo Peretti
*** Bug 23072 has been marked as a duplicate of this bug. *** *** Bug 27800 has been marked as a duplicate of this bug. *** *** Bug 27927 has been marked as a duplicate of this bug. *** *** Bug 28079 has been marked as a duplicate of this bug. *** *** Bug 28880 has been marked as a duplicate of this bug. *** Yes, this is really needed! I should add that right now it is much harder than it should be to convince people to try Eclipse when they are currently using something else and already have the sources on their filesystem (pulled out via standalone CVS, something like TortoiseCVS, or the CVS integration in their existing browser). Noew for them to use Eclipse without having another whole copy of the sources for the projects, they would need to ither have to either: - do a laborious one by one import from the filesystem when instead they should just be able to import all related projects (from a common root or maybe with multi-selects like some file pickers have). - do a laborious checkout of each project one by one so that they can override the location (default is workspace) and point to the existing source location, since when you try to checkout more than one project at a time you no longer are able to specify the target location, they all go into the workspace - and they are unable to use a team project set, since trying to use a team project set all the stuff that is checked out goes into the workspace and you can not set a target directory. Very annoying... We should improve this. Increasing priorioty so it does not get lost. *** Bug 54666 has been marked as a duplicate of this bug. *** What is the status of this bug report? This is fundamental behavior that has been missing for a long time (this bug was file on 2002-08-22), so I hope it makes 3.0. Hi all, there is a plugin available from http://eclipse-tools.sourceforge.net/projecttransfer/ or http://eclipse-plugins.2y.net/eclipse/plugin_details.jsp?id=599 which does allow importing of multiple projects. However I've not investigated it in any great depth, and it appears not to allow for automatically importing projects you depend upon from within the same project root, though I could well be wrong about that bit. It also states that it only works with version 3.0 of eclipse. It is a definite improvement though on the current situation, I'd at least recommend looking into it. Hope this helps. This may not be looked at for 3.1. Moving to Tod so that someone is listening to comments on this bug. Marking as helpwanted: please feel free to contribute a patch. I will up the priority of this to P2 as the vote count is high. We could either change the existing project wizard to allow the selection of several projects or another wizard could be written that does this. This is listed as helpwanted as it is not currently on our list of items for 3.1 (we may get to it if we have time). However if you wish to submit a suggested patch to the Import existing project wizard we can look at it and see if it satisfies everyones requirements. WizardExternalProjectImportPage and ExternalProjectImportWizard are exposed as API. IMHO can be left unchanged because we can create a new page. But the JavaDoc of ExternalProjectImportWizard talks about one project. I mean the WizardExternalProjectImportPage can be left unchanged. *** Bug 56522 has been marked as a duplicate of this bug. *** *** Bug 57045 has been marked as a duplicate of this bug. *** *** Bug 43457 has been marked as a duplicate of this bug. *** Given the high number of votes for this bug a new multi-project wizard has been released to 3.1 M4. Please see Bug 76417 and Bug 40493 for more features related to this wizard. I tried this out against HEAD and found a couple of minor problems: - While it is good that it lets you import projects in the default workspace location, it should not let you select projects that already exist in the workspace (since importing such a project will fail). When searching for .project files in the file system, it could use IWorkspaceRoot.findFilesForLocation followed by checking IFile.exists() to filter out .project files for existing projects. - It seems to kick off one auto-build per project being imported. Looks like it's missing a WorkspaceModifyOperation to wrap the entire import. Verified in 20041214 |