Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 321067 - [Import/Export] Import existing projects from multiple root directories
Summary: [Import/Export] Import existing projects from multiple root directories
Status: RESOLVED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.6   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact: Prakash Rangaraj CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-27 16:46 EDT by Andrew Mak CLA
Modified: 2010-10-05 01:30 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Mak CLA 2010-07-27 16:46:41 EDT
I'm opening this enhancement on behalf of a customer.

The customer would like, in the Import Existing Projects wizard, to be able to select multiple root directories.

The rationale of the request is:

- The customer has a workspace directory with many files/folders in it, including a number of projects that they want to import.
- When selecting this workspace as the root directory in the import wizard, Eclipse will take a long time to scan the contents of the directory for importable projects.
- On the other hand, since the customer knows which projects they want to import, they can select the project directory as the root directory.  However, this means they need to repeat the import for each project.

Therefore, if it's possible to select multiple root directories, then the import can be done much quicker.
Comment 1 Prakash Rangaraj CLA 2010-10-04 07:24:53 EDT
(In reply to comment #0)
> - When selecting this workspace as the root directory in the import wizard,
> Eclipse will take a long time to scan the contents of the directory for
> importable projects.

   How big is the workspace directory and how long Eclipse takes to scan the contents of the directory?
Comment 2 Andrew Mak CLA 2010-10-04 14:18:38 EDT
Unfortunately, I don't have specific numbers on size of the workspace directory and time it takes to load in the customer's environment.  Suffice to say it was large enough that the delay was perceivable by the customer.

It's possible that that are some non-projects directories in that workspace directory that contributes to the loading time, since I notice Eclispe will scan into those subdirectories as well.
Comment 3 Prakash Rangaraj CLA 2010-10-05 01:30:27 EDT
In general we have seen that it doesn't take too much time to scan those directories (even if it scans recursively) to find the projects. Unless we find any serious performance issues in the current model, I wouldn't prefer to fix this.

If you can produce any solid numbers pointing to the performance issues, please reopen with those details.