Community
Participate
Working Groups
User-Agent: Mozilla/5.0 (X11; U; Linux i686; fr; rv:1.9.1.1) Gecko/20090715 Firefox/3.5.1 Build Identifier: Build id: 20090920-1017 Since I move to Eclipse 3.5, sometimes when I update a library in a project, Eclipse complains that it can't delete the bin directory. Here is the complete message : The project was not built due to "Could not delete '/IsisV2/bin/res'.". Fix the problem, then try refreshing this project and building it since it may be inconsistent Sometimes when I refresh the project, the compilation starts, sometimes I must delete the directory in navigator view (where there is no problem to delete the directory). I have a colleague that also moves from 3.4 to 3.5 and the same problem appears. He works on the same project. Sometimes Ant tasks launched from Eclipse also fail to delete directories. I have no file explorer launched in those directories. The -clean option didn't changed anything. I searched the bugs but I didn't find a similar problem reported recently. Reproducible: Sometimes Steps to Reproduce: 1.Update a library in a Java project 2.Sometimes the project can't be built.
What do you mean by "update"? You replace x.jar with an identically x.jar that is of another version? You alter the project's build path through the user interface to point from x-1.2.3.jar to x-1.2.4.jar?
No matter what modification is done. In my case, I replace a jar file by another file (with the same name). When Eclipse detects that the jar is modified, it launches the comilation of the workspace. But when I change project build path, I have the same problem.
Maybe something (Ant task?) is touching your files outside Eclipse? >Steps to Reproduce: >1.Update a library in a Java project >2.Sometimes the project can't be built. This works fine for me. We need more detailed steps.
Are you sure that the file in the bin folder are in sync before you start the compilation ?
I see what sounds like the same problem with eclipse 3.7.2. It happens quite often when I update on my Windows 7 VM (using subclipse 1.6.18) but never on linux. I'm pretty sure that they're not running an ant build or otherwise modifying stuff in the background. That's probably not very helpful but its all the information I've got I'm afraid. In my experience this kind of thing is often caused by no closing an output stream which on Windows will prevent the directory from being deleted (but on linux you get away with it).
Same here, it happens sometimes after i (re)start the IDE. The Workbench was cleanly shutdown via File->Exit. Workspace settings were saved. There were no external changes on the bin folders between shutdown and starting points. My workspace is quite large (~200 Projects) and at least one complete rebuild instead of using the saved build state every morning is annoying. I can't trace it back to a svn update operation. Happens with Version: Indigo Service Release 2 Build id: 20120216-1857 If i can provide any more information, please let me know. Log Entry: Contains: Problems encountered while deleting files. Contains: Could not delete: C:\Virtual Machines\Workspace\odis\branch.2.1.5\EfaMgmt\shared\bin\de\xxx\efamgmt. Contains: Could not delete: C:\Virtual Machines\Workspace\odis\branch.2.1.5\EfaMgmt\shared\bin\de\xxx. Contains: Could not delete: C:\Virtual Machines\Workspace\odis\branch.2.1.5\EfaMgmt\shared\bin\de\xxx. Contains: Could not delete: C:\Virtual Machines\Workspace\odis\branch.2.1.5\EfaMgmt\shared\bin\de. !SUBENTRY 1 org.eclipse.core.resources 4 273 2013-10-08 15:04:26.363 !MESSAGE Problems encountered while deleting resources. !SUBENTRY 2 org.eclipse.core.resources 4 273 2013-10-08 15:04:26.363 !MESSAGE Could not delete '/EfaMgmt_shared/bin/de'. !STACK 1 org.eclipse.core.internal.resources.ResourceException: Problems encountered while deleting resources. at org.eclipse.core.internal.localstore.FileSystemResourceManager.delete(FileSystemResourceManager.java:352)
Well, even with Eclipse 4.3.1, this problem still exists. But according to a colleague, the cause on Windows 7 is the Windows Indexer/Windows Search. If you disable that, you won't get the error anymore.
I can confirm Marcels statement. This works for me.
I have at my Win8 x64 disabled index/search service. But anyway get this error. I don't update any libraries. Only start clean project and get error.
Well, so much for my colleagues remark about the Windows Indexer/Windows Search... :-( But I do have more colleagues with more ideas, and one of them claims that it does not happen when the workspace and sources are located under the user folder. I tried that and indeed it happens much less, but still it does happen occasionally.
For what it's worth, I had the problem on Win 7 and got rid of it by removing my worspace folder from the Windows Search Index.
Note: This problem still occurs with Eclipse Luna every few weeks. The "could not delete" error markers occur always after a restart of Eclipse (after a regular shutdown of Eclipse, not a crash). My environment: Windows 7 Eclipse Java EE IDE for Web Developers / Luna Service Release 1 (4.4.1) The problem can be solved by manually deleting the folders ("refresh" or "clean" does not resolve the problem). IMO this is no "minor" issue as it is very annoying.
Created attachment 270077 [details] The following error displayed on delecting project from Project Explorer Error message:The project was not built due to "Could not delete '/POC/bin/SeleniumWD'.". Fix the problem, then try refreshing this project and building it since it may be inconsi
I can confirm that this bug is still appearing with Eclipse 4.6.3 and Windows 7. Indexing Service is disabled for the Workspace paths.
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.
