Bug 58589 - Problems encountered while deleting resources
Summary: Problems encountered while deleting resources
Status: RESOLVED DUPLICATE of bug 58652
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: 3.0   Edit
Assignee: Kent Johnson CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-04-14 22:02 EDT by devender CLA
Modified: 2004-09-23 15:55 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description devender CLA 2004-04-14 22:02:46 EDT 
Hi,

I am getting an error while compiling my codes with the following description 
"The project was not built due to "Problems encountered while deleting 
resources.". Fix the problem, then try refreshing this project and rebuilding 
it since it may be inconsistent."

Do not which resource(folder ) to delete, and the defect description does not 
have much information.

Can some body help me !!!!!
Comment 1 Bruce Whittaker CLA 2004-05-18 18:48:46 EDT 
I'm getting this too. I would make this a P1 if I could because while I'm in
this state the compiler no longer generates class files, so I'm kind of dead in
the water. I'm running Eclipse 2.13 on Windows XP.
Comment 2 Ralf Hauser CLA 2004-07-05 11:21:50 EDT 
Got the same error message - it would be really helpful to know which file was
blocked by another program...
Comment 3 John Arthorne CLA 2004-07-05 16:52:25 EDT 
Platform core reports a MultiStatus when deletion fails, and the child status
describes what file it could not delete. This information is not being surfaced
in the JDT error message. You might be able to find more details in the error
log (Window > Show View > Other > PDE Runtime > Error log).
Comment 4 Kent Johnson CLA 2004-09-23 15:55:46 EDT 
Verified that in 3.0 we display the message from the first child of the Multi-
status.

*** This bug has been marked as a duplicate of 58652 ***