Bug 207013

I'm working on a fix for this and it should be done in the next couple of days.
You may also want to try these packages until we get 3.2 in FC5 but they
probably have the same problem:

https://www.redhat.com/archives/fedora-devel-java-list/2006-September/msg00008.html

I think I fixed this in 3.2.0-6.fc6. Can you test and report back. Thanks.

I just tried -- had to jump through a few hoops to get the FC5 version installed
again, and then I updated to 3.2.0-6.fc6 from development. Now, eclipse doesn't
start up at all, and I get the following in workspace/.metadata/.log. I can't
immediately tell what's going on, but for the moment I'm going to have to
uninstall and reinstall because I need to use Eclipse on this machine today. If
you want me to test something else, I should be able to do it tonight.

!SESSION 2006-09-21 09:23:11.116 -----------------------------------------------
eclipse.buildId=M20060629-1905
java.version=1.5.0_06
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
Command-line arguments:  -os linux -ws gtk -arch x86

!ENTRY org.eclipse.osgi 2 1 2006-09-21 09:23:15.060
!MESSAGE NLS missing message: fileInitializer_missingFileName in:
org.eclipse.core.internal.runtime.messages

!ENTRY org.eclipse.core.runtime 2006-09-21 09:23:15.087
!MESSAGE Product org.eclipse.sdk.ide could not be found.

!ENTRY org.eclipse.osgi 4 0 2006-09-21 09:23:15.108
!MESSAGE Application error
!STACK 1
java.lang.RuntimeException: No application id has been found.
	at
org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:56)
	at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
	at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336)
	at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
	at org.eclipse.core.launcher.Main.run(Main.java:977)
	at org.eclipse.core.launcher.Main.main(Main.java:952)

Okay, the above looks like a different bug, because it happened even when I
uninstalled and reinstalled Eclipse.

(In reply to comment #4)
> Okay, the above looks like a different bug, because it happened even when I
> uninstalled and reinstalled Eclipse.

Yeah, bug # 207442 seems similar. Let's track this problem there.

Okay, going back to the problem that this bug is about, I just tried the following:
- Reinstall the FC5 Eclipse
- Update to eclipse* from development
- Install eclipse-sdk and all of its friends

It actually seems to have got worse; now, "About Eclipse SDK Features" says that
*all* of the core components are version 3.1.2, even though I'm definitely
running a 3.2.0 Eclipse. Actually, it thinks that JDT is version "-Z4XP", which
is probably even worse, and causes similar error messages to those I typed above
except with JDT and that version instead of RCP and 3.1.2. I'll attach a
screenshot of the "Features" window shortly.

Created attachment 136913 [details]
Screenshot of "Features" window, showing weird versions

What version are you updating from?

The default from FC5 updates: 3.1.2-1jpp_15fc

I'd like to reproduce your problem exactly. Can you provide a list of eclipse
pacakges you have installed on FC5 and provide the command you are using to
update Eclipse from development? Thanks.

Seems to be okay now with eclipse 3.2.1-4.fc6 ... must have been something
transient.

(In reply to comment #11)
> Seems to be okay now with eclipse 3.2.1-4.fc6 ... must have been something
> transient.

Acutally, Andrew Overholt fixed this over the weekend. Thanks for filing the bug.