I am writing an Eclipse plugin using Eclipse RCP (Kepler). Everything was working fine until last night all the sudden I started getting null pointer exceptions when trying to test my plugin. Here is a snippit of the stacktrace:
!ENTRY org.eclipse.ui.workbench 4 2 2013-08-24 08:36:17.616
!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.ui.workbench".
!STACK 0
java.lang.NullPointerException
at org.eclipse.equinox.internal.p2.ui.sdk.scheduler.migration.MigrationSupport.getLastMigration(MigrationSupport.java:229)
at org.eclipse.equinox.internal.p2.ui.sdk.scheduler.migration.MigrationSupport.baseChangedSinceLastPresentationOfWizard(MigrationSupport.java:190)
at org.eclipse.equinox.internal.p2.ui.sdk.scheduler.migration.MigrationSupport.performMigration(MigrationSupport.java:69)
at org.eclipse.equinox.internal.p2.ui.sdk.scheduler.AutomaticUpdateScheduler.earlyStartup(AutomaticUpdateScheduler.java:89)
at org.eclipse.ui.internal.EarlyStartupRunnable.runEarlyStartup(EarlyStartupRunnable.java:87)
at org.eclipse.ui.internal.EarlyStartupRunnable.run(EarlyStartupRunnable.java:66)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.internal.Workbench$55.run(Workbench.java:2552)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
java.lang.NullPointerException
at org.eclipse.core.internal.runtime.InternalPlatform.getLog(InternalPlatform.java:354)
at org.eclipse.core.runtime.Plugin.getLog(Plugin.java:291)
at org.eclipse.ui.internal.WorkbenchPlugin.log(WorkbenchPlugin.java:830)
at org.eclipse.ui.statushandlers.StatusManager.logError(StatusManager.java:285)
at org.eclipse.ui.statushandlers.StatusManager.handle(StatusManager.java:200)
at org.eclipse.ui.statushandlers.StatusManager.handle(StatusManager.java:231)
at org.eclipse.ui.statushandlers.StatusManager$StatusManagerLogListener.logging(StatusManager.java:305)
at org.eclipse.core.internal.runtime.RuntimeLog.logToListeners(RuntimeLog.java:160)
at org.eclipse.core.internal.runtime.PlatformLogWriter.logged(PlatformLogWriter.java:100)
at org.eclipse.equinox.log.internal.ExtendedLogReaderServiceFactory.safeLogged(ExtendedLogReaderServiceFactory.java:86)
at org.eclipse.equinox.log.internal.ExtendedLogReaderServiceFactory.logPrivileged(ExtendedLogReaderServiceFactory.java:205)
at org.eclipse.equinox.log.internal.ExtendedLogReaderServiceFactory.log(ExtendedLogReaderServiceFactory.java:178)
at org.eclipse.equinox.log.internal.ExtendedLogServiceFactory.log(ExtendedLogServiceFactory.java:65)
at org.eclipse.equinox.log.internal.ExtendedLogServiceImpl.log(ExtendedLogServiceImpl.java:87)
at org.eclipse.equinox.log.internal.LoggerImpl.log(LoggerImpl.java:54)
at org.eclipse.core.internal.runtime.PlatformLogWriter.logging(PlatformLogWriter.java:43)
at org.eclipse.core.internal.runtime.RuntimeLog.log(RuntimeLog.java:96)
at org.eclipse.core.runtime.SafeRunner.handleException(SafeRunner.java:71)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:44)
at org.eclipse.ui.internal.Workbench$55.run(Workbench.java:2552)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
To try and figure out what might be going on I went to the launch configuration for my plugin and clicked "Validate Plug-ins" and get the following error:
org.apache.xmlrpc
Missing Constraint: Import-package: javax.xml.bind; version="0.0.0"
Could this be the reason why launching my plugin is failing? If so, how to I fix it?
Thank you
You can right click on your project, go to Run as -> Run configurations and to Plug-ins tab. Here click on the Add required plug-ins button and this should solve your validation problem automatically.
I had to remove following plugins in my run configuration "Eclipse Application" to get rid of the xmlrpc warning:
org.apache.xmlrpc
org.eclipse.mylyn.bugzilla.core
org.eclipse.mylyn.bugzilla.ui
org.eclipse.mylyn.commons.xmlrpc
The xmlrpc warning already occures with
Fresh download of Eclipse RCP, Oxygen
New plugin created with the "Hello World, Command" template
Windows7
Since Oxygen the xmlrpc issue does not occur in the console but as an extra popup window, which I find even more annoying and confusing. The console shows following additional output:
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [bundleresource://555.fwk1347294617:1/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [bundleresource://555.fwk1347294617:2/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [ch.qos.logback.classic.util.ContextSelectorStaticBinder]
08:49:41.650 [Worker-1] INFO c.g.t.t.d.PublishedGradleVersions - Gradle version information cache is up-to-date. Trying to read.
!SESSION 2017-09-04 08:49:32.846 -----------------------------------------------
eclipse.buildId=4.7.0.I20170612-0950
java.version=1.8.0_144
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=de_DE
Framework arguments: -product org.eclipse.platform.ide
Command-line arguments: -product org.eclipse.platform.ide -data D:\eclipse\workspace/../runtime-EclipseApplication -dev file:D:/eclipse/workspace/.metadata/.plugins/org.eclipse.pde.core/Eclipse Application/dev.properties -os win32 -ws win32 -arch x86_64 -consoleLog
!ENTRY org.eclipse.egit.ui 2 0 2017-09-04 08:49:41.847
!MESSAGE Warning: The environment variable HOME is not set. The following directory will be used to store the Git
user global configuration and to define the default location to store repositories: 'C:\Users\eis'. If this is
not correct please set the HOME environment variable and restart Eclipse. Otherwise Git for Windows and
EGit might behave differently since they see different configuration options.
This warning can be switched off on the Team > Git > Confirmations and Warnings preference page.
Could this be the reason why launching my plugin is failing?
I guess not. My plugin does not seem to be influenced by those warnings.
The git warning can be disabled in the Eclipse Team preferences, as the warning itself suggests.
The slf4j warning can be resolved by removing the plugin ch.qos.logback.slf4j, also see multiple slf4j bindings in Eclipse RCP Plugin
If you manually change the plugin selection, please be careful and use the Validate Plug-ins feature to make sure you don't create other dependency issues.
If you have additional plugins installed, you might see even more warnings, e.g. from checkstyle:
!ENTRY org.eclipse.ui 2 0 2017-09-04 10:09:32.926
!MESSAGE Warnings while parsing the commands from the 'org.eclipse.ui.commands' and 'org.eclipse.ui.actionDefinitions' extension points.
!SUBENTRY 1 org.eclipse.ui 2 0 2017-09-04 10:09:32.926
!MESSAGE Commands should really have a category: plug-in='net.sf.eclipsecs.ui', id='CheckstylePlugin.PurgeCaches', categoryId='net.sf.eclipsecs'
!ENTRY org.eclipse.ui 2 0 2017-09-04 10:09:33.622
!MESSAGE Warnings while parsing the commands from the 'org.eclipse.ui.commands' and 'org.eclipse.ui.actionDefinitions' extension points.
!SUBENTRY 1 org.eclipse.ui 2 0 2017-09-04 10:09:33.622
!MESSAGE Commands should really have a category: plug-in='net.sf.eclipsecs.ui', id='CheckstylePlugin.PurgeCaches', categoryId='net.sf.eclipsecs'
=>It's kind of a mess. Therefore it might be a good idea to make a copy of the "default" warnings that can be ignored. Then it will be easier to see if a warning is related to your own plugin/recent changes.
Edit
I filed a bug for the checkstyle warnings and thanks to Lars Koedderitzsch they will be resolved with version 8.5.0:
https://sourceforge.net/p/eclipse-cs/bugs/428/
After trying different stuff: I did:
help>Install new software
and added this repository:
http://download.eclipse.org/tools/orbit/downloads/drops/R20190226160451/repository
taken from orbit: https://download.eclipse.org/tools/orbit/downloads/drops/R20190226160451/
select the ones related with .javax, xml stream
It worked for me.
Eclipse Modeling Tools
Version: 2019-03 (4.11.0)
win 10
If you have EclipseLink 2.5.2 installed then it is a known bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=456174
To fix, update to the latest version using this update site: http://download.eclipse.org/rt/eclipselink/updates/
Choose a newer version than 2.5.2
NOTE: I had to uncheck the "Hide installed version" checkbox to install after adding the update site as it seemed to think it was installed though it showed the software as NOT being installed when I unchecked the box.
Once you have installed the newer version you restart Eclipse and then:
1. Select menu: Run -> Run Configurations
2. Click the button "Add Required Bundles"
It should all work fine after that
If you are trying an RCP E4 application with features, try add org.eclipse.e4.rcp to your dependencies in the product -> dependencies pane. And do "add required". That solved my problem
If you simply want to ignore these errors, you can go to Run > Run Configurations > Plug-ins, and uncheck "Validate Plugin-ins automatically prior to launching" at the bottom.
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 have two local plugin projects in eclipse, both maven projects.
AvgPowerTool
AvgPowerCommon
AvgPowerTool is dependent on AvgPowerCommon (It uses classes from AvgPowerCommon).
When I run the application and try to instantiate a class from AvgPowerCommon the application exits with an exception:
java.lang.RuntimeException: No application id has been found.
Above it, in the log I see:
!ENTRY org.eclipse.equinox.app 0 0 2015-06-02 12:08:10.113
!MESSAGE Product AvgPowerTool.product could not be found.
!ENTRY AvgPowerTool 2 0 2015-06-02 12:08:10.164
!MESSAGE Could not resolve module: AvgPowerTool [208]
Unresolved requirement: Require-Bundle: AvgPowerCommon
This is how the required plugins in AvgPowerTool's plugin.xml look:
What can I do to resolve this?
Thanks.
When running an RCP using 'Run > Eclipse Application' you need to make sure that all the required plugins are checked in the 'Run Configuration' for the application (on the Plugins tab).
If you subsequently build the RCP using an xxx.product file you must list all the required plugins (or features) in the product file.
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
Today I was running into problems with eclipse, like every time I closed a project a window popped up saying something like "error saving workspace" and complaining about apache xerces.
I decided to download a fresh install, and now it won't even start. I tried many variants (classic, javase, c++), hoping there was some distribution issues, but nothing worked. Eclipse starts saying "an error has occurred, see configurationlog ..."
Any idea? Are there some cached files in the system that might have become corrupted? I tried doing a "find / | grep eclipse" but found nothing interesting.
Thanks a lot for your help, I'm quite in trouble without it
Regards,
Nicola Montecchio
p.s. I tried also with 32 bit jvm but nothing changed
[edit] here is relevant bits of the log produced when starting:
!ENTRY org.eclipse.osgi 4 0 2010-07-23 21:35:16.835
!MESSAGE An unexpected runtime error has occurred.
!STACK 0
javax.xml.parsers.FactoryConfigurationError: Provider org.apache.xerces.jaxp.SAXParserFactoryImpl not found
!ENTRY org.eclipse.osgi 4 0 2010-07-23 21:35:16.839
!MESSAGE
!STACK 0
org.osgi.framework.ServiceException: Exception in org.eclipse.core.runtime.internal.adaptor.EclipseAdaptorHook$ParsingService.getService()
!ENTRY org.eclipse.equinox.registry 4 0 2010-07-23 21:35:16.840
!MESSAGE Could not parse XML contribution for "org.eclipse.ant.core//plugin.xml". Any contributed extensions and extension points will be ignored.
!STACK 0
org.xml.sax.SAXException: Could not acquire XML parsing service.
and several other mostly related to xml ...
Sounds like your current workspace is severely broken. Create a new workspace and import the projects from the old locations (File -> Import), and see if that helps.
Things I'd try are renaming your workspace (so Eclipse will use a fresh one when starting up) or running Eclipse with the -clean parameter (in the console with ./eclipse -clean in your eclipse/ folder).