Bug 42391 - ImageBuilderInternalException in FileSystemResourceManager.copy
Summary: ImageBuilderInternalException in FileSystemResourceManager.copy
Status: RESOLVED INVALID
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Resources (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Resources-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-09-02 10:54 EDT by Knut Radloff CLA
Modified: 2004-02-12 16:10 EST (History)
1 user (show)

See Also:


Attachments
log file (3.45 KB, text/plain)
2003-09-02 10:55 EDT, Knut Radloff CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Knut Radloff CLA 2003-09-02 10:54:39 EDT
build 20030828

I have a file linked to a path variable.
The path variable is bound to a file that does not exist.
The project the linked file is in does not compile. 
See the attached log.
Comment 1 Knut Radloff CLA 2003-09-02 10:55:19 EDT
Created attachment 5936 [details]
log file
Comment 2 Knut Radloff CLA 2003-09-02 10:56:48 EDT
Also, I can't delete the file. I get a message "Resource is out of sync with 
the file system" if I try.
Comment 3 John Arthorne CLA 2003-09-10 12:35:51 EDT
It can't copy the file because it doesn't exist on disk (I think this is fine).
 It reports that the file is out of sync because it exists in the workspace but
not on disk.  The navigator correctly allows the user to delete out of sync
resources, but it looks like the package explorer does not.  Moving to JDTUI. 
See DeleteResourceAction for an example of deleting out of sync resources.. it
should prompt for deleting out of sync, then invoke core delete method again
with IResource.FORCE flag.
Comment 4 Dirk Baeumer CLA 2003-09-10 13:49:50 EDT
There are two issue: deleting the file and compiling. The original complain 
was about compiling. Moving to JDT/Core for comments. I opened a separate PR 
for the delete case.
Comment 5 Knut Radloff CLA 2003-09-10 14:24:19 EDT
As far as I remember there was no decent error reporting to help the user 
determine what is wrong. I had to look at the stack dump in the log to find out 
how to get the project to compile. The Problems view only reported that the 
project could not be built.
Comment 6 Kent Johnson CLA 2003-09-24 14:04:45 EDT
We report the resource exception message as part of our build error.

Can Core could include the path of the resource which failed to copy, instead 
of "Problems encountered while copying resources"
Comment 7 John Arthorne CLA 2003-10-03 15:34:13 EDT
The core API returns an exception that contains a MultiStatus.  The child status
says:

Resource /Playground_Knut/testLink does not exist.

In normal API usage, the MultiStatus would be passed to an ErrorDialog, which
would manifest the child status in the "details" area of the dialog. In the java
builder's use, the complete information is not surfaced in the error message
attached to the marker.  
Comment 8 John Arthorne CLA 2004-02-12 16:10:51 EST
There is no core bug here.