| Summary: | Import from file system does not create new project | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Dave Thomson <Dave_Thomson> |
| Component: | UI | Assignee: | Tod Creasey <Tod_Creasey> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | P2 | CC: | n.a.edgar |
| Version: | 2.0 | Keywords: | usability |
| Target Milestone: | 2.0 M6 | ||
| Hardware: | All | ||
| OS: | other | ||
| Whiteboard: | |||
|
Description
Dave Thomson
We can't do (2) since there are other kinds of importers that do not care if there are no projects, e.g. import external project, or import external plug- ins and fragments. Should do (1), or change the wizard page to just show a simple warning message if it can't be completed. Creating a project would mean that the user would have to go through all of the project creation wizards before we import anything. We had previously decided that this would make the import wizard confusing due to the complexity of creating projects (which can be as much as 4 or 5 pages now). We could add in the message on startup of the file and zip import wizard that there are no projects in the workspace. Changed so that if there is no project avaialable the File and Zip import both come up with an error message saying Cannot import into a workspace with no open projects. Please create a project before importing. Marking as closed. |