Community
Participate
Working Groups
This is happening on 3.3 M5. I'm opening this on PDE first, but feel free to move to equinox if more appropriate. I have a runtime workspace, launching with Eclipse 3.3 M5 itself as target platform and the splash screen is not being closed after launch. One thing to note is that some errors appear on error log on target workspace. Also, this 3.3 M5 target was updated using Europa update site. Because of the changes on launcher on M5, I suspect this can have something to do with this bug. eclipse.buildId=I20070209-1006 java.version=1.6.0 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=pt_BR Framework arguments: -launcher C:\eclipse-3.3-M5\eclipse -name Eclipse 600 -product org.eclipse.sdk.ide -pdelaunch Command-line arguments: -launcher C:\eclipse-3.3-M5\eclipse -name Eclipse 600 -product org.eclipse.sdk.ide -data C:\Documents and Settings\Willian\runtime-workspace -dev file:C:/eclipse/workspace-myprojects/.metadata/.plugins/org.eclipse.pde.core/Runtime Workspace/dev.properties -pdelaunch -os win32 -ws win32 -arch x86 Warning Thu Feb 22 03:48:35 GMT-03:00 2007 The following is a complete list of bundles which are not resolved, see the prior log entry for the root cause if it exists: Bundle update@plugins/org.eclipse.equinox.common_3.3.0.v20070122.jar [36] was not resolved. Another singleton version selected: org.eclipse.equinox.common_3.3.0.v20061117 Bundle update@plugins/org.eclipse.osgi_3.3.0.v20070208.jar [70] was not resolved. Another singleton version selected: org.eclipse.osgi_3.3.0.v20061213 eclipse.buildId=I20070209-1006 java.version=1.6.0 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=pt_BR Framework arguments: -launcher C:\eclipse-3.3-M5\eclipse -name Eclipse 600 -product org.eclipse.sdk.ide -pdelaunch Command-line arguments: -launcher C:\eclipse-3.3-M5\eclipse -name Eclipse 600 -product org.eclipse.sdk.ide -data C:\Documents and Settings\Willian\runtime-workspace -dev file:C:/eclipse/workspace-myprojects/.metadata/.plugins/org.eclipse.pde.core/Runtime Workspace/dev.properties -pdelaunch -os win32 -ws win32 -arch x86 Error Thu Feb 22 03:48:44 GMT-03:00 2007 Problems occurred when invoking code from plug-in: "org.eclipse.equinox.app". java.lang.NoSuchMethodError: org.eclipse.osgi.service.runnable.StartupMonitor.applicationRunning()V at org.eclipse.equinox.internal.app.EclipseAppHandle$1.run(EclipseAppHandle.java:185) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.equinox.internal.app.EclipseAppHandle.applicationRunning(EclipseAppHandle.java:175) at org.eclipse.core.internal.runtime.InternalPlatform.endSplash(InternalPlatform.java:152) at org.eclipse.core.runtime.Platform.endSplash(Platform.java:540) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2198) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2103) at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:457) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:452) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:101) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:146) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:104) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:74) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:170) 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:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:476) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:416) at org.eclipse.equinox.launcher.Main.run(Main.java:1124) at org.eclipse.equinox.launcher.Main.main(Main.java:1099) It is worth to note that, like the message said, there are 2 org.eclipse.equinox.common_3.3.0 bundles on the target platform. Looking at the jar timestamp, looks like the older was created by some of Europa update site. Launching the runtime workspace with the clean flag does not work. Disabling the older org.eclipse.equinox.common_3.3.0 bundle on plugin list/launch configuration does not help too (it is strange to note that when you enter the launch configuration dialog again, it will be enabled automatically...).
Wassim can you explain why PDE is launching with the osgi.framework property set to the old version of org.eclipse.osgi?
yes I can. The user must have an old osgi imported into his workspace.
(In reply to comment #1) > Wassim can you explain why PDE is launching with the osgi.framework property > set to the old version of org.eclipse.osgi? > Do you mean, the 2 equinox versions? Like I said, I'm using my own 3.3 M5 installation as target platform, and some update site would have installed the older version. Yes, I suspect that removing manually all older bundles would resolve this problem (although I haven't tested yet), but the point is that I'd like to let you know if there is some bug here, because I presume this is a perfectly valid situation (having multiple versions installed). Let me know if you need some more information.
The message "Another singleton version selected: org.eclipse.osgi_3.3.0.v20061213" does not seem to indicate that org.eclipse.osgi is checked out from CVS, otherwise it would have "qualifier" instead of "v20061213" as the qualifier. Maybe it was imported into the workspace from the target before you updated the target? Willian, do you have a org.eclipse.osgi project in your workspace?
(In reply to comment #4) > Willian, do you have > a org.eclipse.osgi project in your workspace? > I'll confirm later at home, but I'm 99,99% sure that I don't.
I think the answer may lie in comment 3. If there are two versions of the osgi plugin in the target, PDE launches with both versions (now that we support multiple versions), and one gets arbitrarily picked for the config.ini. In this case, we should pick the highest. However, when parsing the target platform, PDE asks Update Manager to give us a list of bundle URLs from the target location. So if Update Manager was used to dowload plug-ins and create a platform.xml, then only one osgi version would have been passed to PDE and the rest of the osgi versions would have been ignore right from the start. Was Update Manager used properly here? or is the target a collection of old/new bundles assembled by hand?
I got the steps to reproduce: - Start a clean 3.3 M5 installation. - Start update manager, search for new features on "Europa Discovery Site". - Expand "Enabling features", select only "Eclipse Project Equinox bundle feature 3.3.0.v20061016--etc...". Install it. - Restart Eclipse, create a new Eclipse Application launch configuration. - Launch it. Gotcha! Now try to edit the launch configuration, unchecking the older equinox.common on plugins tab, apply and launch again. The bug still occur, and the next time you open the launch configuration, for some unknown reason the plugin will still be checked.
Wassim, were you able to reproduce using the steps described on comment#7? I'm afraid that the Europa update site will be updated soon with new contents due to M5 release, and we possibly won't be able to reproduce with the original steps.
moving to inbox.
The steps are no longer applicable. Please reopen if this issue still affects you in a more recent build.
