Community
Participate
Working Groups
Build ID: M20060921-0945 Steps To Reproduce: Trying to move projects via the Navigator view to a read-only destination does not flag an error and corrupts the project. Please reproduce the problem as follows: 1- Create a new project (any type, eg. Java, Dynamic Web, etc.) 2- In the navigator view, right-click the project and select Move. 3- The 'Move Project' dialog comes up. Uncheck 'Use default location', then enter a location that is read-only (eg. a CD-ROM) 4- Click OK. Note that there is no validation of the location and you get an error message similar to this: Problems encountered while moving resources. Problems encountered while moving resources. Could not move: /dynaweb. Could not move: D:\jan18\dynaweb. Cannot create file because existing file of wrong type exists: Z:\. Problems encountered while setting project description. Cannot create file because existing file of wrong type exists: Z:\. Errors occurred during refresh of resource: /dynaweb. Errors occurred while refreshing resources with the local file system. The project description file (.project) for dynaweb is missing. This file contains important information about the project. The project will not function properly until this file is restored. You will also get errors after workspace build attempts, eg: Errors during build. Errors running builder "Integrated External Tool Builder" on project dynaweb. The builder launch configuration could not be found. 5- In the Navigator view, there appear to be no files under the project directory anymore. The Project Explorer view is similarly incomplete. (the project files have not actually been deleted from the file system). More information:
I verified this is broken in 3.4M6. The ProjectContentsLocationArea class is the place to start to look at a fix. It does not call a method to verify that the actual URI can be written to.
As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009
*** Bug 368372 has been marked as a duplicate of this bug. ***
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
