Eclipse caster

I have a maven project in eclipse indigo with m2e 1.2.0.20120903-1050 maven plugin. This project contains maven system dependencies, and these jar files are checked into the git repository.

This is normal until I need to switch to another branch that has changes in the system dependencies. git cannot update content because the file is locked.

The eclipse seems to be on its own or on behalf of the blocked jar libraries. I tried to close the project, but this does not help, in order to release the lock, I need to restart eclipse.

This is rather cumbersome. Is there any trick to release the lock without restarting eclipse?

+4
source share
6 answers

Window

You can use handle.exe with http://technet.microsoft.com/de-de/sysinternals/bb896655.aspx

  • handle.exe .jar gives you a list by handle id and process id for all jar's .
  • handle.exe -c <handle-id> -p <process-id> kills the handle, maybe an exception will be thrown, if so, fill out the error message for the Eclipse error system to inform us of deadlocks.
+3
source

This is not a problem with Windows. This is a problem with something that Eclipse does. Saving a file for the duration of the Eclipse run. This is a terrible practice.

+2
source

You can download Sysinternals Suite from Microsoft and use handle.exe or procexp.exe to find which program has the descriptor on the bank. It seems safe to close the handle in Eclipse (I have not noticed any side effects).

The sysinternals website describes how to use handle.exe , and for procexp.exe use the option Find β†’ Find Handle or DLL. Enter the name of the locked jar file, then select the locking process in the sub-window. In the main window, it should show the file descriptor in the process, you can check if this is the process that you think so, then right-click and select "Close descriptor".

You must complete both of these tasks with administrator privileges.

There are other guides on the net:

+2
source

No. If the files are open, git cannot delete them. This is a Windows case.

I would advise you instead to install them in a local repository instead of dealing with the system area,

+1
source

I also had problems with this. It turns out that this is caused by indexing Windows files. I am using Windows 7. I went to the control panel and selected the indexing options. I will definitely delete any folder in which my code was located. This solved my problem.

+1
source

I have the same problems as when using RAD (eclipse). In my case, this happens when decompiling with the JD-Eclipse plugin (1.0.0). I have no problem installing the latest Eclipse Mars (4.5.1) and JD-Eclipse (1.0.0). I suspect that the basic version of eclipse (4.2.1) in the RAD version is not compatible with JD-Eclipse (1.0.0) when working.

0
source

All Articles