'Building workspace' has encountered an error
Solution 1
Try next steps:
- Go to your eclipse installation folder
- Run "eclipse.exe -clean"
- Work normally
- Enjoy
Solution 2
I ran into this same issue and I believe the culprit to be the Sonarqube plugin I had installed.
This discussion pointed me in that direction:
Uninstalled the Sonarqube plugin and the error is gone.
Solution 3
I uninstalled my Netbeans because Eclipse and Netbeans are both usin the same workspace.
i uninstalled Netbeans and the error is gone.
Solution 4
In my case, the problem resulted to be my Eclipse was running on an outdated IBM Java Virtual Machine. I updated my IBM JRE, I modified my eclipse.ini in order to update the -vm parameter so it points to the new installation, and it solved the problem.
Solution 5
I keep my Workspace on Dropbox. I had this issue occur, and managed to solve it by searching within [workspace]/.metadata/ for the word 'conflicted' and deleting all these files Dropbox had created. Error was gone when I restarted Eclipse.
KaOCode
Updated on April 21, 2020Comments
-
KaOCode about 4 years
Eclipse Luna 4.4.0
Error occurred during the Build
Error instantiating builder 'ord.eclipse.m2e.core.maven2Builder'. Plug-in org.eclipse.m2e.core was unable to load class org.eclipse.m2e.core.internal.builder.MavenBuilder An error occurred while automatically activating bundle org.eclipse.m2e.core (547). Plug-in org.eclipse.m2e.core was unable to load class org.eclipse.m2e.core.internal.builder.MavenBuilder. An error occurred while automatically activating bundle org.eclipse.m2e.core (547). Error instantiating builder 'org.eclipse.m2e.core.maven2Builder'. Plug-in org.eclipse.m2e.core was unable to load class org.eclipse.m2e.core.internal.builder.MavenBuilder. An error occurred while automatically activating bundle org.eclipse.m23.core (547). Plug-in org.eclipse.m2e.core was unable to load class org.eclipse.m2e.core.internal.builder.MavenBuilder. an error occurred while automatically activating bundle org.eclipse.m2e.core (547).
if i delete the folder
.metadata
and all.project
and.setting
data from my workspace, i get no error. After one day of work i´ll get the same error. -
jordanpg over 9 yearsSame issue. Installing the SonarQube plugin brought eclipse to its knees. Will file bug report with SQ soon.
-
gp. about 9 yearsI had changed jdk version in eclipse.ini. clean launch fixed the issue.
-
simpleusr about 9 yearsThis also worked for me too. Thanks!!! PS: I got this error after updating m2e plugin in. There was another eclipse instance running during the update. I think this was the problem...
-
Satya about 9 yearsRunning -clean worked for me. On Mac this command is '/Applications/eclipse\ 3/Eclipse.app/Contents/MacOS/eclipse -clean'
-
miloxe almost 9 years-clean helped Luna 4.4.1
-
Pawel almost 8 yearsAlso helped on Mars
-
TheBat over 7 yearsWorked for Neon.1
-
Benny over 7 yearsI am using Neon 1, but i got this issue only on 1 project from github the error is:
Errors occurred during the build. Errors running builder 'Android Package Builder' on project 'ProjectName'. Could not initialize class com.android.tools.lint.checks.BuiltinIssueRegistry
-
Joaquín L. Robles over 4 yearsDidn't work for me, instead I changed the -vm argument in eclipse.ini and it did the trick
-
Stephen Kennedy about 2 yearsExcellent thanks!