Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 367815

Summary: Error after deleting a lib from library folder (Java Model Exception)
Product: [Eclipse Project] JDT Reporter: Alessio Pollero <alessio.pollero>
Component: CoreAssignee: Jay Arthanareeswaran <jarthana>
Status: VERIFIED NOT_ECLIPSE QA Contact:
Severity: normal    
Priority: P3 CC: alessio.pollero, amj87.iitr, satyam.kandula
Version: 3.7   
Target Milestone: 3.8 M6   
Hardware: PC   
OS: Windows 7   
Whiteboard:
Attachments:
Description Flags
eclipse error log none

Description Alessio Pollero CLA 2012-01-04 04:07:33 EST 
Build Identifier: Version: 3.7.1 Build id: M20110909-1335

I have a project where i have created a folder where i put jar files related to the project, after copying the files inside this directory i usually add the library to the build path.

When i want to remove a library from the project i go to the build path list, then i remove the library (with right click and remove from build path), then to completely remove the library from the project i go to the lib folder and delete the library jar file, after doing that i get this error : 

!ENTRY org.eclipse.ltk.ui.refactoring 4 10000 2012-01-04 09:55:51.584
!MESSAGE Internal Error
!STACK 1
Java Model Exception: Core Exception [code 273] Problems encountered while deleting resources.

If i restart eclipse after removing the library from build path, then when i try to delete the file from the library folder everything works well.

Reproducible: Always

Steps to Reproduce:
1.Remove a library from Build path
2.Go to the lib folder and delete the jar file of the library
Comment 1 Alessio Pollero CLA 2012-01-04 04:08:23 EST 
Created attachment 208987 [details]
eclipse error log
Comment 2 Ayushman Jain CLA 2012-01-05 07:07:04 EST 
I think a possible workaround should be to refresh the project after deleting from build path and then delete the jar from the lib folder.
Jay, can you please follow up? Thanks!
Comment 3 Jay Arthanareeswaran CLA 2012-01-05 23:38:00 EST 
Did you mean you get the error when you remove the jar from the build path? Or are you trying to remove the JAR from eclipse itself, say package explorer?

Can you check if the JAR was open in another application? I am unable to reproduce the bug. But it would help if you can attach the log file.
Comment 4 Alessio Pollero CLA 2012-01-06 04:00:27 EST 
The error happen after that i delete the jar file from the library in package explorer, the only program that keep opened the file is eclipse itself, because when i close and reopen eclipse then i succeed with the delete .

The error happen after that a dialog with a progress bar indicating the file delete progression is close to the end (100%) .

The error log is already attached to this bug.
Comment 5 Jay Arthanareeswaran CLA 2012-01-06 06:46:44 EST 
(In reply to comment #4)
> The error happen after that i delete the jar file from the library in package
> explorer, the only program that keep opened the file is eclipse itself, because
> when i close and reopen eclipse then i succeed with the delete .
> 
> The error happen after that a dialog with a progress bar indicating the file
> delete progression is close to the end (100%) .
> 
> The error log is already attached to this bug.

How did you add this particular jar (beansbinding-1.2.1.jar) to the classpath? As external JARs or library/variable? Could you try a couple of things for me, because I am not able to reproduce the problem: Can you try the same steps with a different library? If possible, can you attach your workspace?
Comment 6 Alessio Pollero CLA 2012-01-08 14:08:02 EST 
beansbinding-1.2.1.jar is a library used by WindowBuilder to let the user to bind a component in the UI to a bean, maybe the problem is that WindowBuilder still kept opened the library, but in that case i shouldn't be able to remove from the build path, isn't it ?

However to test this case you have to install WindowBuilder plugin then create a lib folder in your project, copy beansbinding.jar library, then right click on it and add to the build path, after that you should see the binding tab in window Builder editor, so you can try to remove the library in the way i done ...
Comment 7 Jay Arthanareeswaran CLA 2012-01-08 21:13:41 EST 
(In reply to comment #6)
> beansbinding-1.2.1.jar is a library used by WindowBuilder to let the user to
> bind a component in the UI to a bean, maybe the problem is that WindowBuilder
> still kept opened the library, but in that case i shouldn't be able to remove
> from the build path, isn't it ?

No, removing from build path shouldn't be affected. However deleting involves a resource delete, which would be affected if the file is open by some other client.
Comment 8 Jay Arthanareeswaran CLA 2012-02-01 11:02:10 EST 
I don't think we can do anything here. The resource is being used by another application, which means the resource can't deleted from eclipse.
Comment 9 Satyam Kandula CLA 2012-03-14 05:11:28 EDT 
I am not able to reproduce the problem by using a library jar. I didn't try with the WindowsBuilder plugin. I also think that the jar is open by some plugin causing this problem.
Verified for 3.8M6.