I get this SO exception when building the workspace.
!ENTRY org.eclipse.core.jobs 4 2 2014-06-27 16:01:29.327
!MESSAGE An internal error occurred during: "Rebuilding".
!STACK 0
java.lang.StackOverflowError
at org.eclipse.jdt.internal.compiler.lookup.ParameterizedTypeBinding.mentionsAny(ParameterizedTypeBinding.java:915)
at org.eclipse.jdt.internal.compiler.lookup.ParameterizedTypeBinding.mentionsAny(ParameterizedTypeBinding.java:915)
My workspace has a lot of projects, with a lot of compile errors, which I'm trying to resolve.
Any clues why this might happen?
Windows 8.1
JDK 8 build 05
Eclipse for RCP and RAP Developers
Luna Release (4.4.0)
Build id: 20140612-0600
This looks like Eclipse bug 432541 or the duplicate 434800.
Unfortunately these bugs are still open.
Update: This bug is now marked as fixed in Eclipse Luna 4.4.1 (and subsequent releases).
Related
After starting Eclipe I see the following error message in the workspace/.metadata/.log
!ENTRY org.eclipse.core.runtime 4 0 2017-09-18 09:38:48.275
!MESSAGE Invalid input url:platform:/plugin/com.mountainminds.eclemma.ui/icons/full/eview16/coverage.gif
!STACK 0
java.io.IOException: Unable to resolve plug-in "platform:/plugin/com.mountainminds.eclemma.ui/icons/full/eview16/coverage.gif".
The message does not go away even after uninstalling or reinstalling the plugin.
Any ideas on how to resolve this?
Eclipse: Oxygen 4.7.0
EclEmma: 3.0.0
EclEmma became an Eclipse project and is now part of the Eclipse Java download packages. Due to the move, the plug-ins have been rename: com.mountainminds.eclemma.ui become org.eclipse.eclemma.ui.
If you use a workspace that have been used with EclEmma < 3.0.0 before,
start Eclipse with the option -clean and
reset all Java perspectives (coverage.gif is the icon of the Coverage view and could be referenced in the stored window/perspective layout).
This is the image the error is referring to.
Put it in the proper installation path on your machine and you'd be fine.
When using the Eclipse Jetty plugin (http://marketplace.eclipse.org/content/eclipse-jetty?mpc=true&mpc_state=), I started to get the following error:
An internal error occurred during: "Launching myProject".
Unknown scope: test,provided
This started to occur for two separate projects, both on Windows and MacOs X systems. Note that a regular Jetty deployment, as well as the Jetty runner Maven plugin, work like a charm, the problem seems to be with the Eclipse plugin only. The problem persists after upgrading the plugin to the newest version. Changing Jetty versions doesn't help as well.
edit: Thanks for the tips so far. The question is what might be the source of this problem and how to get rid of it. The relevant log message is as follows:
!ENTRY org.eclipse.core.jobs 4 2 2016-04-27 09:01:40.914
!MESSAGE An internal error occurred during: "Launching myProject".
!STACK 0
java.lang.IllegalArgumentException: Unknown scope: test,provided
at net.sourceforge.eclipsejetty.util.MavenScope.to(MavenScope.java:109)
at net.sourceforge.eclipsejetty.util.MavenDependencyInfo.create(MavenDependencyInfo.java:98)
at net.sourceforge.eclipsejetty.util.MavenDependencyInfoMap.resolve(MavenDependencyInfoMap.java:141)
at net.sourceforge.eclipsejetty.util.Dependency.create(Dependency.java:39)
at net.sourceforge.eclipsejetty.launch.util.JettyLaunchConfigurationDelegate.getOriginalClasspathEntries(JettyLaunchConfigurationDelegate.java:340)
at net.sourceforge.eclipsejetty.launch.util.JettyLaunchConfigurationDelegate.createJettyConfigurationFile(JettyLaunchConfigurationDelegate.java:791)
at net.sourceforge.eclipsejetty.launch.util.JettyLaunchConfigurationDelegate.getVMArguments(JettyLaunchConfigurationDelegate.java:217)
at org.eclipse.jdt.launching.JavaLaunchDelegate.launch(JavaLaunchDelegate.java:64)
at net.sourceforge.eclipsejetty.launch.util.JettyLaunchConfigurationDelegate.launch(JettyLaunchConfigurationDelegate.java:192)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039)
at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Try running Eclipse with a console and debug info to see if more error details are available: add -console, -consoleLog and -debug to your eclipse.ini to achieve this.
Try using the Run Jetty Run plugin instead of the Maven Jetty plugin
I installed JDK-1.8_20 and Eclipse Luna in Linux Mint 16. When I clicked Eclipse Marketplace form menu, Eclipse Luna crashed (Eclipse IDE closed abrubtly). I checked the following answers but those answers are not matched with my scenarios:
Eclipse Marketplace hangs (Luna, Java8)
Market Place not working in Eclipse Luna
Is it possible to resolve this issue?
Update:
I have added log from /workspace/.metadata/.log file:
!ENTRY org.eclipse.core.resources 2 10035 2014-10-13 20:32:16.558
!MESSAGE The workspace exited with unsaved changes in the previous session; refreshing workspace to recover changes.
!ENTRY org.eclipse.m2e.logback.configuration 2 0 2014-10-13 20:32:17.080
!MESSAGE Exception while setting up logging:org.eclipse.osgi.internal.framework.EquinoxConfiguration$1 cannot be cast to java.lang.String
!STACK 0
java.lang.ClassCastException: org.eclipse.osgi.internal.framework.EquinoxConfiguration$1 cannot be cast to java.lang.String
at org.eclipse.m2e.logback.configuration.LogHelper.logJavaProperties(LogHelper.java:26)
at org.eclipse.m2e.logback.configuration.LogPlugin.loadConfiguration(LogPlugin.java:189)
at org.eclipse.m2e.logback.configuration.LogPlugin.configureLogback(LogPlugin.java:144)
at org.eclipse.m2e.logback.configuration.LogPlugin.access$2(LogPlugin.java:107)
at org.eclipse.m2e.logback.configuration.LogPlugin$1.run(LogPlugin.java:62)
at java.util.TimerThread.mainLoop(Timer.java:555)
at java.util.TimerThread.run(Timer.java:505)
I had this problem as well. I had to change a GTK theme to fix it.
Put following into the ~/.config/gtk-3.0/settings.ini file:
[Settings]
gtk-theme-name = Adwaita
gtk-fallback-icon-theme = gnome
This seems to be related with both GTK2 and GTK3 starting in the same process.
the workaround is to use GTK2 for eclipse as well. This can be achieved in the following ways
1. add the following lines to eclipse.ini before -vmargs(recommended approach)
--launcher.GTK_version
2
2. set the environment variable SWT_GTK3 to 0 before launching eclipse. you need to do this every time you launch eclipse
Source: https://bugs.eclipse.org/bugs/show_bug.cgi?id=438598#c16
when i navigate in project tree (such as open package, etc) their always show error message box :
An internal error occurred during: "Decoration Calculation".
org/eclipse/jdt/internal/debug/ui/MemberActionFilter
and this is the log in /.workspace/.log :
!ENTRY org.eclipse.core.jobs 4 2 2013-11-01 17:29:23.513
!MESSAGE An internal error occurred during: "Decoration Calculation".
!STACK 0
java.lang.NoClassDefFoundError: org/eclipse/jdt/internal/debug/ui/MemberActionFilter
at org.eclipse.jdt.internal.debug.ui.ActionFilterAdapterFactory.getAdapter(ActionFilterAdapterFactory.java:42)
at org.eclipse.core.internal.runtime.AdapterManager.getAdapter(AdapterManager.java:295)
at org.eclipse.core.runtime.PlatformObject.getAdapter(PlatformObject.java:66)
at org.eclipse.ui.internal.util.Util.getAdapter(Util.java:110)
at org.eclipse.ui.internal.ActionExpression$ObjectStateExpression.getActionFilter(ActionExpression.java:471)
at org.eclipse.ui.internal.ActionExpression$ObjectStateExpression.preciselyMatches(ActionExpression.java:524)
at org.eclipse.ui.internal.ActionExpression$ObjectStateExpression.isEnabledFor(ActionExpression.java:499)
at org.eclipse.ui.internal.ActionExpression$SingleExpression.isEnabledFor(ActionExpression.java:743)
at org.eclipse.ui.internal.ActionExpression.isEnabledFor(ActionExpression.java:1053)
at org.eclipse.ui.internal.decorators.DecoratorDefinition.isEnabledFor(DecoratorDefinition.java:281)
at org.eclipse.ui.internal.decorators.DecoratorManager.getDecoratorsFor(DecoratorManager.java:382)
at org.eclipse.ui.internal.decorators.LightweightDecoratorManager.getDecoratorsFor(LightweightDecoratorManager.java:315)
at org.eclipse.ui.internal.decorators.LightweightDecoratorManager.getDecorations(LightweightDecoratorManager.java:340)
at org.eclipse.ui.internal.decorators.DecorationScheduler$1.ensureResultCached(DecorationScheduler.java:371)
at org.eclipse.ui.internal.decorators.DecorationScheduler$1.run(DecorationScheduler.java:331)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
FYI, I'am using Eclipse for Java EE (Kepler)
on Ubuntu 13.10 64bit
sorry for my english :D
I had the same problem with kepler on Debian Jessie.
But i realized that eclipse started with a second flying window i detached in my last session to compare to classes. I told eclipse to "Reset Perspective" in Windows menu and restarted. That did the trick.
Close to Eclipse
Copy to yout project (projects) from workspace to temp dir
Remove ./workspace/.metadata
Run Eclipse and import yout project with copy source code
I have Eclipse (Juno SR2) with both M2E (1.3), M2E-WTP (0.17) and WebSphere Dev Tools for v.8. The problem started after Websphere Dev tools installation. It says in error dialog : "Validating" "org/eclipse/m2e/wtp/MavenWtpPlugin".
In Eclipse logs it turned out to be NoClassDefFoundError
!MESSAGE An internal error occurred during: "Validating <module name here>".
!STACK 0
java.lang.NoClassDefFoundError: org/eclipse/m2e/wtp/MavenWtpPlugin
Does anyone had some luck in solving this issue?
Thanks!
The missing class is in fact there, plugin org.eclipse.m2e.wtp. Started to dig in the IBM WAS Dev Tools.
The problem originates from com.ibm.etools.maven.javaee.core plugin.
Checked MANIFEST.MF under \plugins\com.ibm.etools.maven.javaee.core_1.1.0.v20130522_1924\ and it turned out there is some strange version range bundle dependency on org.eclipse.m2e.wtp;bundle-version="[1.0.0,2.0.0)";resolution:=optional. The plugin org.eclipse.m2e.wtp version is not even close to version 1.0.0 and resolution is optional, so made some changes to conform the bundle resolution:
...,org.eclipse.m2e.wtp;bundle-version="[0.1.0,2.0.0)";resolution:=optional,...
Started Eclipse with -clean argument, and refreshed all Maven projects in the workspace.
This seems to do the trick for me. You may still get
"Updating Maven Project". Unsupported IClasspathEntry kind=4
but there is a fix for this already here "Updating Maven Project". Unsupported IClasspathEntry kind=4