Bug 1070554 - unable to start eclipse due java.lang.RuntimeException: Application "org.eclipse.ui.ide.workbench" could not be found in the registry.
Summary: unable to start eclipse due java.lang.RuntimeException: Application "org.ecli...
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: eclipse
Version: rawhide
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Roland Grunberg
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-27 05:13 UTC by Filipe Rosset
Modified: 2014-04-10 10:15 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-04-03 14:28:07 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
initialization log (32.54 KB, text/x-log)
2014-02-27 05:13 UTC, Filipe Rosset
no flags Details

Description Filipe Rosset 2014-02-27 05:13:50 UTC
Created attachment 868329 [details]
initialization log

unable to start eclipse due java.lang.RuntimeException: Application "org.eclipse.ui.ide.workbench" could not be found in the registry.

log attached.

Comment 1 Alexander Kurtakov 2014-02-27 07:57:09 UTC
Can you verify you have at least eclipse-4.3.1-20.1.fc21 ? You might have hit the time between batik update and the eclipse rebuild for it.

Comment 2 Filipe Rosset 2014-02-27 13:44:15 UTC
Ok, my version is 4.3.1-19.fc21.x86_64 I'm waiting for mirrors synchronization, because there are no updates available here ATM.

Comment 3 Filipe Rosset 2014-03-06 14:41:26 UTC
Sorry, but it stills broken in rawhide:

stack trace:
http://paste.fedoraproject.org/82965/39411671

eclipse/batik versions:
http://paste.fedoraproject.org/82966/41167741

Comment 4 Roland Grunberg 2014-03-06 15:14:44 UTC
There has been a very recent (yesterday) update to batik (Bug 1073110) that prevented Eclipse from starting up on rawhide. batik-1.8-0.14.svn1230816.fc21 will be needed. Also, the latest Eclipse on rawhide currently is eclipse-4.3.1-23.fc21 . With these fixes it should be possible to start Eclipse on rawhide, but there are still some more changes needing to have all functionality. A lot of these changes are recent so it may take some time for the mirrors to sync unless latest repos are used.

Comment 5 Filipe Rosset 2014-03-07 02:48:38 UTC
OK guys, now I'm able to start eclipse with these installed packages:
http://paste.fedoraproject.org/83242/13941601

But only few options are available, eg, lack of rpm-dev-tools, etc:
http://postimg.org/image/6pc96myvb/

Comment 6 Roland Grunberg 2014-03-10 18:16:43 UTC
I see the same thing. In fact Eclipse doesn't seem to generate the user's profile / bundles.info, which is probably why you don't see the capabilities of the non-platform plugins. I'm currently working through some dependency issues, and problems with the lucene 4 update, but if those don't fix the issue, I'll have to take a closer look.

Comment 7 Roland Grunberg 2014-03-11 19:49:56 UTC
http://koji.fedoraproject.org/koji/taskinfo?taskID=6622808 is currently building and should provide 4.3.1-24.2 . I tested this out and it should fix the remaining issues.

Comment 8 Roland Grunberg 2014-04-03 14:28:07 UTC
Marking as CLOSED (RAWHIDE). Note that the latest version of Eclipse in Rawhide seems to be Eclipse Luna 4.4.0 M6 ( + changes since), and I can confirm it works for me (eclipse-4.4.0-0.5.git201404011500.fc21).

Comment 9 Aidan Delaney 2014-04-10 10:05:37 UTC
I'm seeing this issue after installing eclipse-4.4 from rawhide on Fedora 20

# rpm -qa | grep eclipse
eclipse-m2e-sourcelookup-1.1.0.201401182304-1.fc21.noarch
eclipse-wtp-sourceediting-3.5.1-2.fc20.noarch
eclipse-emf-core-2.9.2-1.fc20.noarch
eclipse-jdt-4.4.0-0.7.git201404011500.fc21.x86_64
eclipse-m2e-core-1.4.0-11.1.fc20.noarch
eclipse-ecf-core-3.8.0-1.fc20.noarch
eclipse-findbugs-2.0.3-2.fc21.noarch
eclipse-pde-4.4.0-0.7.git201404011500.fc21.x86_64
eclipse-emf-2.9.2-1.fc20.noarch
eclipse-wtp-common-3.5.1-1.fc20.noarch
eclipse-jgit-3.3.1-1.fc20.noarch
eclipse-egit-github-3.0.0-3.fc20.noarch
eclipse-platform-4.4.0-0.7.git201404011500.fc21.x86_64
icu4j-eclipse-52.1-2.fc21.noarch
eclipse-gef-3.9.1-0.2.gitb9f2e9.fc20.noarch
eclipse-emf-xsd-2.9.2-1.fc20.noarch
eclipse-mylyn-3.10.0-1.fc20.noarch
eclipse-equinox-osgi-4.4.0-0.7.git201404011500.fc21.x86_64
eclipse-wtp-servertools-3.5.1-1.fc20.noarch
eclipse-m2e-egit-0.14.0-0.1.git571dc0a.fc20.noarch
eclipse-swt-4.4.0-0.7.git201404011500.fc21.x86_64
eclipse-dtp-1.11.2-1.fc20.noarch
eclipse-eclemma-2.3.0-1.fc21.noarch
eclipse-p2-discovery-4.3.1-1.fc20.noarch
eclipse-egit-3.3.1-1.fc20.noarch

Last bit of the log is:
!ENTRY org.eclipse.osgi 4 0 2014-04-10 11:05:02.413
!MESSAGE Application error
!STACK 1
java.lang.RuntimeException: Application "org.eclipse.ui.ide.workbench" could not be found in the registry. The applications available are: org.eclipse.ant.core.antRunner, org.eclipse.equinox.app.error, org.eclipse.equinox.p2.director, org.eclipse.equinox.p2.garbagecollector.application, org.eclipse.equinox.p2.publisher.InstallPublisher, org.eclipse.equinox.p2.publisher.EclipseGenerator, org.eclipse.equinox.p2.publisher.ProductPublisher, org.eclipse.equinox.p2.publisher.FeaturesAndBundlesPublisher, org.eclipse.equinox.p2.reconciler.application, org.eclipse.equinox.p2.repository.repo2runnable, org.eclipse.equinox.p2.repository.metadataverifier, org.eclipse.equinox.p2.artifact.repository.mirrorApplication, org.eclipse.equinox.p2.metadata.repository.mirrorApplication, org.eclipse.equinox.p2.updatesite.UpdateSitePublisher, org.eclipse.equinox.p2.publisher.UpdateSitePublisher, org.eclipse.equinox.p2.publisher.CategoryPublisher, org.eclipse.help.base.infocenterApplication, org.eclipse.help.base.helpApplication, org.eclipse.help.base.indexTool, org.eclipse.jdt.core.JavaCodeFormatter, org.eclipse.jdt.core.JavaIndexer.
	at org.eclipse.equinox.internal.app.EclipseAppContainer.startDefaultApp(EclipseAppContainer.java:248)
	at org.eclipse.equinox.internal.app.MainApplicationLauncher.run(MainApplicationLauncher.java:29)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:379)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:233)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
	at org.eclipse.equinox.launcher.Main.main(Main.java:1438)

Comment 10 Alexander Kurtakov 2014-04-10 10:15:23 UTC
(In reply to Aidan Delaney from comment #9)
> I'm seeing this issue after installing eclipse-4.4 from rawhide on Fedora 20
> 
In order for this to work - make sure that you have glassfish*, jetty*, objectweb-asm*, tomcat*, lucene*, etc. from rawhide too. Otherwise eclipse will fail to resolve bundles resulting in the application not being resolved (exactly your case).


Note You need to log in before you can comment on or make changes to this bug.