MyEclipse: delete/replace a jar file will fail MichaelClavier - Apr 24, 2012 - 09:35 AM Post subject: delete/replace a jar file will fail
Hi,
when trying to delete or replace a jar file I will often get the following error message:
Problems encountered while deleting resources.
Could not delete 'D:\WS\work\workspace 86\EARGwin\lib\utils.jar'.
Problems encountered while deleting files.
Could not delete: D:\WS\work\workspace 86\EARGwin\lib\utils.jar.
There is no external server process running. Even directly after having MyEclipse restarted the error will remain.
The jar-file is part of an EAR project, which is referenced by two other projects, one EJB, the other WEB. EJB an Web project are combined as Enterprise application projects. The error remains, regardless of having the EAR deployed or not.
I am working on MyEclipse 9.1, Build id: 9.1-20110701.
Regards,
Michaelsupport-swapna - Apr 24, 2012 - 11:13 AM Post subject:
Michael,
Sorry that you are seeing this issue.
1. Can you share the installation details from MyEclipse > Installation Summary > Installation Details ? Paste them here for us.
2. Can you please update to our latest release 10.1 and check if you still see the issue ?
You can install 10.1 alongside 9.1 version and the license which you hold for 9.1 is valid for 10.1 too as our licenses are time based and not version based.
3. If you are still seeing the issue, please give us detail steps you are following right from EAR creation to the way you are trying to delete the jar for us to help replicate it at our end.MichaelClavier - Apr 25, 2012 - 08:01 AM Post subject:
Swapna,
thanks for supporting me.
1. Installation Summary is:
*** Date:
Mittwoch, 25. April 2012 08:46 Uhr MESZ
** System properties:
OS=Windows7
OS version=6.1.0
Java version=1.7.0
2. I would so much like to install MyEclipse 10.1.
As the last updates showed me, this will take not just downloading and installing time but also upgrading projects and correcting things and so on.
I will find one or two days to be able to do so as far as project plans will allow it.
3. I still see the issue.
The way I delete the jar file: select the file in package explorer, then press Del-Button and press OK.
The way I replace the jar file: select the jar file, open context menu, choose replace/latest from head (or branch), press OK
In both cases the error will be shown, the jar file can't be removed.
The EAR project is an project with the following structure:
EARProject:
- lib/utils.jar et al
- configured with the modules
- EJBProject
- WEBProject
- EJBProject
- classpath references to ../EARProject/lib/utils.jar
Removing EJBProject and WEBProject from EARProject's modules does not solve the problem.
Do you have any idea?
Regards,
Michaelsupport-swapna - Apr 26, 2012 - 07:44 AM Post subject:
MichaelClavier,
Thank you for the details. I could not replicate the issue at my end.
1. Clear the contents of the .log file which is located at <workspace dir>/.metadata/.log, now try deleting the jar file and copy paste the contents of the .log file here for us.
2. Can you please switch to a new workspace, create a sample project and check if you see the same issue ?
Let us know how it works for you.MichaelClavier - Apr 26, 2012 - 08:42 AM Post subject:
Swapna,
attached you will find the .log-file.
I'll try to create a sample project as soon as I am able to.
Regards,
MichaelMichaelClavier - May 21, 2012 - 07:16 AM Post subject: MyEclipse 10.0 - same error
Swapna,
I was now able to install MyEclipse 10.1.
Unfortunately the deletion results in the same error as in ME 9.1.
Kind regards,
Michaelsupport-swapna - May 22, 2012 - 08:32 AM Post subject:
MichaelClavier,
Sorry that you are still seeing the issue.
Can you give us some more information to help investigate further?
1.Which source control system are you working with?
2. How are you checking out the files initially for use in MyEclipse (e.g. checking out externally or from within MyEclipse, and is it whole projects or individual files/folders) ?
3. Can you check if you can delete the file outside of MyEclipse, from Windows Explorer or from a command line ?
4. Can you also recheck if there is any other program that might have the jar file open ?MichaelClavier - May 22, 2012 - 08:46 AM Post subject:
Swapna,
1.source control system is CVS.
2. The files are checked out from within MyEclipse into a workspace directory. The files are checked out as a complete CVS project.
3. The files can also not be deleted from outside MyEclipse. The only posibility to delete the files is to close MyEclipse, then delete the files with Explorer for example.
4. There is definitely no other process that might have the files opened.
Michaelsupport-swapna - May 22, 2012 - 11:14 AM Post subject:
MichaelClavier,
Thank you for the details.
Can you try turning off the "Build Automatically" to see if there is a builder which is holding on to the jar file ?
Restart the IDE after turning off the "Build Automatically" and try deleting the jar file.
Let us know it works for you.MichaelClavier - May 22, 2012 - 11:18 AM Post subject:
Swapna,
build automatically deactivated, restarted - but deletion results in failure, the file cannot be deleted.
Sorry,
Michaelsupport-swapna - May 23, 2012 - 06:04 AM Post subject:
Michael,
Thank you for trying our recommendations. We tried to replicate the issue with the information you provided but we do not see the issue at our end.
I installed process explorer. The result is to be seen in the attachment.
Hope it'll bring you further.
Kind regards
Michaelsupport-swapna - May 24, 2012 - 08:45 AM Post subject:
Michael,
Thank you for trying and confirming that it is indeed a MyEclipse process which is holding the lock for the jar. We still are unable to replicate the issue at our end.
Can you please give us some more information?
1. Do you have any third party plugins installed ? If yes, please list them for us.
2. Can you send us the .project file for the referencing project for further investigation ?
3. Can you please try to close editors and perspectives related to Jasper to find out what is holding the file, while trying to delete the jar after each close.
4. Can you also confirm that this is the only jar that is locked and other jars that have the same dependency are not locked ? Also recheck if you can delete any other jar in the EAR/lib with no dependencies.MichaelClavier - May 24, 2012 - 09:08 AM Post subject:
Swapna,
ad 1. yes, all plugins should be listed in configuration details (see attachment)
ad 2. .project of the referencing project - renamed as .project.txt, as it is not allowed to attach .project files
ad 3. as far as I know, there is no jasper process running on my computer.
If you think that there is a jasper process, please tell me how to identify them.
ad 4. no, this is not the only jar file. I tried to rename/delete 10 out of 40, none of them can be renamed/deleted.
Hope this helps,
Michaelsupport-swapna - May 24, 2012 - 10:36 AM Post subject:
Michael,
Thank you for the files. We are looking at them.
Even if there are no known Jasper editors or perspectives open, please close the editors and perspectives one by one, to try to find out what is locking the files.
If you cannot find what is locking the files, then close the referencing project and check if you can delete the jar file.MichaelClavier - May 24, 2012 - 12:03 PM Post subject:
Swapna,
I closed the editors one by one and checked whether the jar's could be deleted.
After all editors are closed, the jar files are still not deletable.
I closed then all perspectives. Same here, no deletion possible.
Michaelsupport-tony - May 25, 2012 - 05:13 AM Post subject:
Michael,
We are going through your list of plugins to try to find out what is locking those files. No luck so far.
Please try closing the referencing project (the one with the jar file in the classpath), and try to delete the file, as Swapna asked in her last post. This will tell us if there is some plugin functionality connected to that project that is locking the files. Could you tell us what tools/plugins you are using in that project (including things like code analysis tools)?
Also, please try a fresh workspace, import those two projects into it and see if the file can be deleted there, without doing anything else. I'm thinking that there is some view open that is locking the files but a fresh workspace is probably the quickest way to check that.MichaelClavier - May 25, 2012 - 07:09 AM Post subject:
Tony,
I already did - and now checked again to close all referencing projects. The jar file cannot be deleted.
Also I had closed all perspectives and views - same result, no deletion possible.
What tools/plugins I use? We defined the JBoss 5.1's location and deploy the EAR-project to it. But even removing this deployment won't make the file to be deletable.
In EAR's Enterprise Application Module definiton we defined an EJB and a WEB project. Both are referencing the EAR project in their build paths, as they use classes from its jar files.
Maybe one or two times I used FindBugs, but not for months and not on a regular base.
What else? I am coding in java, run some tests with JUnit, search in java/jsp/text files - nothing spectacular.
I tried the new workspace thing. The file WAS deletable then.
So to me it will be the easiest to start working in a new workspace.
For you it might be furthermore interesting what created the problem, am I right?
How can I help you in that issue?
Regards,
Michaelsupport-tony - May 25, 2012 - 11:13 AM Post subject:
Thanks for that information, Michael. A clean workspace might be a good option for you. However, I have been able to replicate your problem.
It appears to be related to the Google plug-in. If I have a Google web application that references the jar file, and run the application at least once, then the Google plug-in, or, more specifically, the GWT Designer GPE plug-in, seems to hold a lock on the file. I restarted MyEclipse several times and it always held the lock, even at startup, until I removed the GWT Designer GPE plug-in. However, when I re-installed the plug-in, I couldn't replicate that behavior, though a lock was held on the file for the whole session, whenever I ran the Google web application. I'm guessing I did something else with some of the Google plug-ins, previously, which caused the lock to be held across sessions.
This Google bug appears to be similar to your problem and it contains a workaround that delays some Google plug-in processing at startup. This worked for me. The workaround is to add the following line at the end of your myeclipse.ini file:
Code:
-Dgwtd.warmup.enabled=false
I can't tell if your situation is similar but you have installed the Google plug-in, which led me to replicate and find this possible workaround (or delete the GWT Designer GPE, if you don't need it).
Please let us know if this helps.MichaelClavier - May 25, 2012 - 11:23 AM Post subject:
Tony,
well done - this parameter helps to remove the lock.
Now I am able to rename or delete the jar files.
Even when I removed the MyEclipse parameter after having started MyEclipse once with it I was able to rename or remove the jar file.
Works fine for me - thanks a lot.
Michaelsupport-tony - May 28, 2012 - 07:03 AM Post subject:
Michael,
I'm glad that worked for you and thanks for getting back to us.