Community
Participate
Working Groups
I have some of the projects on my work bench located on a removable volume (this could easily be a network drive) and if I start Eclipse without this volume, then it will create the workspace up to the projects it can't find and then not continue, because an error is generated. This means that I have to reimportant the projects that were created after the projects on the removable drive, since the error aborts further processing. I believe that the workspace should be able to handle this via a warning, rather than an error, so that processing does not get aborted.
Using Eclipse 2.0.2 and 2.1 integration build I20030220, this problem does not happen. A project whose content area is missing appears as closed, and the following message is produced in the log file (the same message is presented to the user on an error dialog if he/she tries to open the project): "The project description file (.project) for B is missing. This file contains important information about the project. The project will not function properly until this file is restored." All other projects are opened normally. In 2.0.2, an error message is presented to the user when closing the workbench: "Problems occurred while trying to save the state of the workbench" Details: "Could not create folder: L:\test" Where "L:\test" is the external location of the project whose contents are in a currently non-available network drive. Note: if the content area is restaured (e.g. the remote file system has been remounted) during a workbench session, the user will be able to successfully open the project and access its resources. I suggest this bug to be closed as FIXED in 2.0.2/2.1 (it was reported against 2.0.1).
Closing.
