Summary: | [import] Import 'Projects from Folder or Archive' silently ignores failure to import already imported projects | ||
---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Dennis Hendriks <dh_tue> |
Component: | IDE | Assignee: | Platform-UI-Inbox <Platform-UI-Inbox> |
Status: | NEW --- | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | CC: | rolf.theunissen, wim.jongman |
Version: | 4.20 | ||
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: |
Description
Dennis Hendriks
2022-03-13 07:11:36 EDT
Dennis, can you take a stab at solving this? The statement that the project cannot be imported is not completely true. As the project is located in the workspace location, the directory name is by definition the project name. For the "Import exiting projects into Workspace" wizard this is implemented in Bug 143757. The "Projects from Folder or Archive" (SmartImport) was introduced with Bug 472614, so Bug 218024 probably refers to the "Import exiting projects into Workspace" wizard and is unrelated. In the SmartImportJob exceptions are caught, but not reported to the user. This was never fixed before. Bug 526490 (attempted) fixed some constraint in the UI, so that no illegal selection could be made. In fact, this change is not consistent with the logic in SmartImport as it 1) assumes that the directory is a project directory and 2) only considers the directory name and not the project name in the .project file. In this reported case, the directory name is allowed but the name from the .project file is not allowed. This also fails when the project is not located in the workspace. (In reply to Wim Jongman from comment #1) > Dennis, can you take a stab at solving this? I am already looking into this, but (once again) it is not as small as expected. At least I have partial fixes ready. |