I recently let STS update itself from 3.1 to 3.5 and now I'm getting errors regarding the MatchLocator class. I'm not sure what MatchLocator is, but it appears to be a core Eclipse service.
When I open STS I get 'Initializing Java Tooling' has encountered a problem.
An internal error occurred during: "Initializing Java Tooling".
org/eclipse/jdt/internal/core/search/matching/MatchLocator
After it's open I get an error marker for each applicationContext.xml in each project that says
java.lang.NoClassDefFoundError: org/eclipse/jdt/internal/core/search/matching/MatchLocator
No lines are marked, just that it's a "Spring Beans Problem"
When I close STS I get Problmes occurred while trying to save the state of the workbench with details:
An internal error occurred during: "Initializing Java Tooling".
org/eclipse/jdt/internal/core/search/matching/MatchLocator
I've tried downloading a fresh copy of STS 3.5 to a separate directory and each of my workspaces still have this error so I suspect the problem is in the .metadata directory. A couple other Stack Overflow posts have recommended deleting the workspace .metadata or .metadata\.plugins directories and letting Eclipse rebuild them for that workspace but that didn't fix it either.
I'm running on a Mac with these plugins: m2e Maven Integration and associated plugins, Scala IDE, STS and StartExplorer.
Is there a way to restore the missing MatchLocator files?
Fixed this by removing this file in each workspace:
[workspace]/.metadata/.plugins/org.eclipse.e4.workbench/workbench.xmi
Opening STS from the command line (on mac: ./STS.app/Contents/MacOS/STS -clean) and viewing stack traces on startup led me to this answer: https://stackoverflow.com/a/13884461/1637003
Now all the random ways this bug was manifesting itself have gone away: JUnit tests not running, cmd+clicking to open declarations not working, various MatchLocator errors on startup and shut down.
One of the simplest solution for this problem is that we have to launch a new eclipse IDE and again we install STS tool plugin then import your project.
It works well and u get free from errors.
Related
I am using latest Eclipse version with cmake4eclipse add-on on my Debian machine. I am a noob at using Eclipse and already there is a problem! The very strange problem is that after building a project the explorer tab of IDE shows the built binary but I can not actually find it using my usual file manager. When I try to run the binary from IDE, Eclipse complaints a nullpointer exception has occurred. What is happening here?
I have a plain Eclipse installation without much of anything, and a workspace with a Maven (or better yet Tycho) project. Everything worked until I decided to change the JDK (Preferences -> Installed JREs); now whenever I start a Maven build or the plug-in unit tests I get the following error:
Error occurred during initialization of VM
java.lang.UnsatisfiedLinkError: java.lang.Class.getClassLoader0()Ljava/lang/ClassLoader;
<<no stack trace available>>
I have restarted Eclipse and tried a different installation, and since I thought the problem was with the JRE, I changed it back to the original one. Still the same error.
The corresponding 64bit JRE works, but sadly the build has an integration test for 32bit (Cannot load 32-bit SWT libraries on 64-bit JVM), so that's why I need to get 32bit to work again.
How do I fix it?
Deleting all the .metadata folder of the workspace and setting it up again helped.
I get an error while trying to update Eclipse (Kepler Service Release 1; Build id: 20130919-0819)
Eclipse wants to update the following package:
Eclipse Standard/SDK 2.0.2.20140224-0000
An error occurred while uninstalling
session context was:(profile=epp.package.standard, phase=org.eclipse.equinox.internal.p2.engine.phases.Uninstall, operand=[R]org.eclipse.rcp.configuration_root.win32.win32.x86 1.0.0.v20130521-1847 --> null, action=org.eclipse.equinox.internal.p2.touchpoint.natives.actions.CleanupzipAction).
Backup of file E:\Program Files (x86)\eclipse\eclipse.exe failed.
Can not remove : E:\Program Files (x86)\eclipse\eclipse.exe
This error also occurs when I try to update as administrator.
Does anybody have any idea what would cause this?
Solution extracted from this forum http://www.eclipse.org/forums/index.php/t/487240/:
Run eclipse
Rename eclipse exe to eclipse.exe.back
Run updates
Updates executed successfully
It worked for me.
See Eclipse kepler can't install updates.
The eclipse update feature seems to mess up a lot of times with broken dependencies and missing configurations.
You can fix them all up manually if you would like to but that would take some time to debug what is wrong and then how to fix it.
The best advise I can give you is to download a fresh copy of the required Eclipse version and then import your workspace in this new Eclipse installation
I am using Rational Application Developer 7.5.3.When I open my workspace it shows "Initializing Java Tooling" - 1% for long time.It gets hanged up when I try to open any file in my workspace.
I have referred How can I disable "Initialize Java Tooling" on Eclipse startup? but couldn't get my problem resolved.
Kindly assist.
Eclipse's Bugzilla has a few bug reports about the product hanging during "Initializing Java Tooling". These bugs seem to have been resolved. You're using RAD 7.5.x which is based off a very old edition of Eclipse, so I wouldn't be surprised if the underlying Eclipse of RAD 7.5.x suffers from those "Initializing Java Tooling" bugs.
I remember encountering many of these "Initializing Java Tooling" hangs in previous versions of RAD, but haven't seen those in quite a while.
You may wish to upgrade to a later RAD version (the latest at the moment is 9.0.1). If that doesn't help, a PMR with IBM would be the way to go.
After installing STS successefuly on Juno, i opened a new MVC project, fixed the errors in the sample STS project by adding all the required spring jars, and now there are 2 problems:
I can't get the option: "Run on server" (altough i did set a tomcat's server in the workspace).
With every step i make (clean, delete etc') i'm getting the follwing error:
Errors occurred during the build.
Errors running builder 'Faceted Project Validation Builder' on project 'First_STS_Project'.
Could not initialize class org.eclipse.jst.j2ee.project.facet.IJ2EEFacetConstants
Errors running builder 'Validation' on project 'First_STS_Project'.
org.eclipse.jst.j2ee.project.facet.IJ2EEFacetConstants
This is not a local problem on my specific workspace, because i getting the same error in my second PC as well.
I don't recommend JUNO since it has many bugs and it also has a bad impact in performance. If you're in Windows, try to use short paths when installing the plugins or selecting the workspace. I have similar issues when working in windows. If I create a workspace in c:/users/Marcelo/Documents/java/workspaces, I always get issues, but whenever I change to "c:/workspaces" directly, works perfectly. Try with Eclipse Indigo instead. Also try to use the latest version of tomcat. If any of the previous recommendations fix the issue, (that could be weird), try to install the STS plugin again but check all the features, maybe a component is missing.