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).
Related
I am updating my eclipse rcp application from 4.16 to 4.22.
If I run my updated eclipse rcp application in an entirely new workspace, it works.
If I run my updated eclipse rcp application on top of an existing workspace that previously ran the 4.16 version, there is this error about not finding an icon (this is the project explorer icon that changed from a gif to a png file):
!ENTRY org.eclipse.jface 4 0 2022-01-31 08:37:13.602
!MESSAGE /icons/full/eview16/resource_persp.gif
!STACK 0
java.io.FileNotFoundException: /icons/full/eview16/resource_persp.gif
at org.eclipse.osgi.storage.url.bundleentry.Handler.findBundleEntry(Handler.java:55)
I tried deleting everything in the workspace except the workpace/.metadata/.plugins/org.eclpse.core.resources
directory before launching my updated application, but it displays an empty application window with the following general error:
!ENTRY org.eclipse.osgi 4 0 2022-01-31 08:47:03.042
!MESSAGE An error occurred while automatically activating bundle com.xxx.xxx.xxx.xx.xxx (15).
!STACK 0
org.osgi.framework.BundleException: Error loading bundle activator.
If I close my application and launch a second time, everything works. The workspace somehow fixes itself.
Any ideas on how to fix my existing workspace before the first launch of my updated application? I do have an installer, so can perform some sort of one time fix.
Other things I have tried that result in a failed first launch, but fixed second launch:
Deleting the workspace/.metadata/.plugins/org.eclipse.e4.workbench/workbench.xmi file
Modifying the workspace/.metadata/.plugins/org.eclipse.e4.workbench/workbench.xmi file to reference resource_persp.png instead of resource_persp.gif
I'm developing some Eclipse plugins (based on xtext) and I tried to update the target definition from 4.6 Neon to 4.8 Photon.
I have a launch configuration that launches an Eclipse IDE with my plugins loaded. After updating the target definition, the launch configuration automatically updated the version numbers of the bundles that come from the target definition. Some of the new versions had new dependencies, which I added with the "Add Required Plug-ins" button. "Validate Plug-ins" finds no issues, however, when I run this launch configuration, it fails with the following exceptions (stack traces omitted):
!ENTRY org.eclipse.e4.ui.workbench 4 0 2018-07-16 17:58:31.550
!MESSAGE Unable to create class 'org.eclipse.e4.ui.internal.workbench.addons.CommandProcessingAddon' from bundle '495'
!STACK 0
org.eclipse.e4.core.di.InjectionException: Unable to process "CommandProcessingAddon.broker": no actual value was found for the argument "IEventBroker".
!ENTRY org.eclipse.e4.ui.workbench 4 0 2018-07-16 17:58:31.559
!MESSAGE Unable to create class 'org.eclipse.e4.ui.internal.workbench.addons.ContextProcessingAddon' from bundle '495'
!STACK 0
org.eclipse.e4.core.di.InjectionException: Unable to process "ContextProcessingAddon.broker": no actual value was found for the argument "IEventBroker".
!ENTRY org.eclipse.e4.ui.workbench 4 0 2018-07-16 17:58:31.568
!MESSAGE Unable to create class 'org.eclipse.e4.ui.workbench.swt.util.BindingProcessingAddon' from bundle '498'
!STACK 0
org.eclipse.e4.core.di.InjectionException: Unable to process "BindingProcessingAddon.broker": no actual value was found for the argument "IEventBroker".
!ENTRY org.eclipse.e4.ui.workbench 4 0 2018-07-16 17:58:31.602
!MESSAGE Unable to create class 'org.eclipse.e4.ui.workbench.addons.splitteraddon.SplitterAddon' from bundle '496'
!STACK 0
org.eclipse.e4.core.di.InjectionException: Unable to process "SplitterAddon.ps": no actual value was found for the argument "EPartService".
!ENTRY org.eclipse.e4.ui.workbench 4 0 2018-07-16 17:58:31.612
!MESSAGE Unable to create class 'org.eclipse.ui.internal.ide.addons.SaveAllDirtyPartsAddon' from bundle '689'
!STACK 0
org.eclipse.e4.core.di.InjectionException: Unable to process "SaveAllDirtyPartsAddon.eventBroker": no actual value was found for the argument "IEventBroker".
I have no idea what could be causing this. The launch configuration worked fine before. Googling these errors hasn't yielded a helpful result.
Most likely the list of auto-started plugins and their runlevels is corrupted. Opening the "Plug-ins" tab in the launch configuration and pressing the "Restore Defaults" button should fix the problem.
If you customized the list of plugins/features you will have to repeat that. (You can store the launch config in a file in the Common tab, make a backup and compare it with the result to make your life easier).
The same problem can also happen with products. In this case, the solution is to open the "Configuration" tab of the product configuration, click the "Remove All" button under "Start Levels", and click "Add Recommended".
Eclipse Neon displays an error message box during startup and will not open. The message gives a file path to a log file. In that file I see this error message:
!ENTRY org.eclipse.e4.ui.workbench.swt 4 2 2016-11-13 08:50:49.856
!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.e4.ui.workbench.swt".
!STACK 0
java.lang.IllegalAccessError: com.aptana.editor.css.CSSSourceEditor.isWordWrapEnabled()Z
at org.eclipse.ui.texteditor.WordWrapToggleAction.isWordWrapEnabled(WordWrapToggleAction.java:66)
at org.eclipse.ui.texteditor.WordWrapToggleAction.update(WordWrapToggleAction.java:57)
at org.eclipse.ui.texteditor.TextEditorAction.<init>(TextEditorAction.java:68)
at org.eclipse.ui.texteditor.WordWrapToggleAction.<init>(WordWrapToggleAction.java:34)
at org.eclipse.ui.texteditor.AbstractTextEditor.createActions(AbstractTextEditor.java:5898)
at org.eclipse.ui.texteditor.AbstractDecoratedTextEditor.createAction
The OS is Ubuntu 16.04
i found this solution and it worked for me.
I went to directory:
.metadata.plugins\org.eclipse.e4.workbench
And renamed
workbench.xmi to workbenchOLD.xmi
I found it here:
org.eclipse.swt.SWTException: “Widget is disposed” when trying to open AndroidManifest.xml
I hope it helped!
See you,
Federico
I am experiencing trouble when starting the Runtime workbench in eclipse. The new eclipse opens up but crashes on the "Loading Workbench" instruction.
I've tried a few things already, namely:
rm -r .metadata
or
./eclipse -clean -clearPersistedState
I also tried to delete the .snap file, the workbench.xmi file, I tried uninstalling and reinstalling Eclipse, this didn't help.
Here's the log from the crash:
!ENTRY org.eclipse.core.net 1 0 2013-11-03 21:44:52.276
!MESSAGE System property http.nonProxyHosts has been set to local|*.local|169.254/16|*.169.254/16 by an external source. This value will be overwritten using the values from the preferences
!ENTRY org.eclipse.ui.workbench 4 2 2013-11-03 21:44:54.013
!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:232)
at org.eclipse.equinox.internal.p2.ui.sdk.scheduler.migration.MigrationSupport.baseChangedSinceLastPresentationOfWizard(MigrationSupport.java:193)
at org.eclipse.equinox.internal.p2.ui.sdk.scheduler.migration.MigrationSupport.performMigration(MigrationSupport.java:71)
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:2551)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
!ENTRY org.eclipse.ui 4 4 2013-11-03 21:44:54.028
!MESSAGE Unhandled Exception
!ENTRY org.eclipse.equinox.p2.ui.sdk.scheduler 4 0 2013-11-03 21:44:54.030
!MESSAGE Unable to execute early startup code for an extension
!STACK 0
java.lang.NullPointerException
at org.eclipse.equinox.internal.p2.ui.sdk.scheduler.migration.MigrationSupport.getLastMigration(MigrationSupport.java:232)
at org.eclipse.equinox.internal.p2.ui.sdk.scheduler.migration.MigrationSupport.baseChangedSinceLastPresentationOfWizard(MigrationSupport.java:193)
at org.eclipse.equinox.internal.p2.ui.sdk.scheduler.migration.MigrationSupport.performMigration(MigrationSupport.java:71)
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:2551)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
Does somebody have a solution to this particular problem? I'm becoming crazy from not finding a solution.
Otherwise, I'll have to format and reinstall everything maybe?
Thank you guys if you can help!
OK after messing around with all eclipse files and stuff, I found the solution:
I had to use a new workspace that wasn't in the parent folder of the current workspace, explanation:
Old workspace:
somefolder/parentfolder/workspace/
Every workspace in the parentfolder/ is corrupted, so each time I was trying a new workspace in this folder, it didn't work
By using this kind of workspace, the problem wasn't there anymore:
somefolder/workspace
My advice to you if this happens: do not only use the parent folder to try a workspace but a completely random other folder.
Hope this helps other people in the same position.
I was getting the same error. I was able to run it using ./eclipse -clean -clearPersistedState but then got another error of "Locking not possible in the directory" and this got resolved by giving 777 permission to eclipse folder and its contents.
This worked for me.
cd /Applications/adt-bundle-mac-x86_64-20140702/eclipse/Eclipse.app/Contents/MacOS
Then inside there you will see two files eclipse and eclipse.ini.
You want to run this command ./eclipse -clean -clearPersistedState
Eclipse will start up, build your workspace, then restart. Then everything is fine. Good to go!
I'm trying to run a headless eclipse build but I'm getting stuck. My context is that I want to use the PyDev code analysis without having to fire up the eclipse gui. I am aware of the other command line tools to do code analysis (pyflakes, pylint, etc).
The command I have so far is:
java -jar /path/to/eclipse/plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar -noSplash -data "/path/to/workspace" -application org.eclipse.jdt.apt.core.aptBuild
My java version 1.6.0_31, my eclipse version is 3.7.2, and my pydev version is 2.5.0.
When I run the command, it looks like it is working, but it never catches any errors or warnings.
...
PyDev: Analyzing 29 of 33 (forms.py)
PyDev: Analyzing 29 of 33 (forms.py)
PyDev: Analyzing 29 of 33 (forms.py)
PyDev: Analyzing 29 of 33 (forms.py)
...
If I tail -f /path/to/workspace/.metadata/.log, I get a huge stack trace:
!ENTRY org.eclipse.equinox.preferences 4 2 2012-07-30 17:48:39.612
!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.equinox.preferences".
!STACK 0
java.lang.ExceptionInInitializerError
at org.eclipse.debug.internal.ui.DebugUIPreferenceInitializer.setDefault(DebugUIPreferenceInitializer.java:186)
at org.eclipse.debug.internal.ui.DebugUIPreferenceInitializer.setThemeBasedPreferences(DebugUIPreferenceInitializer.java:204)
at org.eclipse.debug.internal.ui.DebugUIPreferenceInitializer.initializeDefaultPreferences(DebugUIPreferenceInitializer.java:79)
at org.eclipse.core.internal.preferences.PreferenceServiceRegistryHelper$1.run(PreferenceServiceRegistryHelper.java:281)
..... TRUNCATED ......
!ENTRY org.eclipse.osgi 4 0 2012-07-30 17:48:39.622
!MESSAGE An error occurred while automatically activating bundle org.eclipse.debug.ui (42).
!STACK 0
org.osgi.framework.BundleException: Exception in org.eclipse.debug.internal.ui.DebugUIPlugin.start() of bundle org.eclipse.debug.ui.
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:734)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:683)
at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:381)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:299)
..... TRUNCATED .......
java.lang.IllegalStateException: Workbench has not been created yet.
at org.eclipse.ui.PlatformUI.getWorkbench(PlatformUI.java:92)
at org.eclipse.debug.internal.ui.contextlaunching.LaunchingResourceManager.startup(LaunchingResourceManager.java:546)
at org.eclipse.debug.internal.ui.DebugUIPlugin.getLaunchingResourceManager(DebugUIPlugin.java:315)
at org.eclipse.debug.internal.ui.DebugUIPlugin.start(DebugUIPlugin.java:516)
..... TRUNCATED ......
!ENTRY org.eclipse.osgi 4 0 2012-07-30 17:48:39.624
!MESSAGE An error occurred while automatically activating bundle org.eclipse.debug.core (41).
!STACK 0
org.osgi.framework.BundleException: Exception in org.eclipse.debug.core.DebugPlugin.start() of bundle org.eclipse.debug.core.
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:734)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:683)
at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:381)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:299)
..... TRUNCATED ......
My suspicion is that PyDev needs the gui to render the errors/warnings.
PyDev needs the gui to render errors/warnings and in general it was not done to be used in the command line... now, having said that, it does have unit-tests that run the code-analysis without requiring a gui (nor even eclipse loaded), but you have to configure the interpreter/projects in-memory for that to work.
See:
https://github.com/aptana/Pydev/blob/development/plugins/com.python.pydev.analysis/tests/com/python/pydev/analysis/OccurrencesAnalyzerTest.java
https://github.com/aptana/Pydev/blob/development/plugins/com.python.pydev.analysis/tests/com/python/pydev/analysis/AnalysisTestsBase.java
for tests that do code-analysis without requiring the eclipse workbench to be loaded at all (i.e.: doesn't even need eclipse to be run headless -- it could be run as a simple java program, but you still have to do the java main([]) using PyDev in the CLASSPATH and using its API to properly set the interpreter used in PyDev as well as the projects/pythonpath).
You can take a look at the setUp of the tests (i.e.: don't forget to also look superclasses such as CodeCompletionTestsBase/AnalysisTestsBase).
Note: if you do create such a main([]), please provide a patch for PyDev as it may be used by others...
As an implementation note, such a main should probably gather all the current PYTHONPATH entries from the shell being launched and configure all of those in the interpreter... Also, it should probably receive a directory as a parameter so that it analyzes all files in the tree (the startup is probably going to take the most of your time to configure things, so, ideally analyze as much files as you can from a single run, as the PyDev code-analysis was done to cache lots of things in the startup and then use the information from RAM -- or maybe create a server process that's always live?).