Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Equinox » Upgrade from 3.4.0 to 3.4.1 fails
Upgrade from 3.4.0 to 3.4.1 fails [message #119727] Fri, 17 October 2008 20:31
Matt Baker is currently offline Matt Baker
Messages: 1
Registered: July 2009
Junior Member
I am having trouble using the update manager for 'p2' to update from 3.4.0
to 3.4.1. After the update finishes and I am prompted to restart, the
restart fails with the following errors in the .log file. As part of the
upgrade, our product branding and splash screens have changed because the
config.ini gets rewritten.

A couple of questions:

1. Why is this failing after the upgrade

2. Why does Eclipse rebrand itself after the upgrade / and what can we do
to prevent it.


eclipse.buildId=M20080911-1700
java.version=1.5.0_11
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Framework arguments: -showlocation
Command-line arguments: -os win32 -ws win32 -arch x86 -showlocation

!ENTRY org.eclipse.equinox.app 0 0 2008-10-17 15:41:18.584
!MESSAGE Product org.eclipse.platform.ide could not be found.

!ENTRY org.eclipse.osgi 4 0 2008-10-17 15:41:18.615
!MESSAGE Startup error
!STACK 1
java.lang.IllegalArgumentException: Bundle
"initial@reference :file:plugins/org.eclipse.equinox.p2.reconciler.dropins_1.0. 2.R34x_v20080909.jar/ "
has been uninstalled
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.g etBundleStartLevel(StartLevelManager.java:371)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.ensureBundle sActive(EclipseStarter.java:446)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.startup(Ecli pseStarter.java:335)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:175)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 549)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
at org.eclipse.equinox.launcher.Main.main(Main.java:1212)

!ENTRY org.eclipse.osgi 2 0 2008-10-17 15:41:18.645
!MESSAGE One or more bundles are not resolved because the following root
constraints are not resolved:
!SUBENTRY 1 org.eclipse.osgi 2 0 2008-10-17 15:41:18.645
!MESSAGE Bundle
reference:file:plugins/org.eclipse.update.scheduler_3.2.100. v20080404.jar
was not resolved.
!SUBENTRY 2 org.eclipse.update.scheduler 2 0 2008-10-17 15:41:18.645
!MESSAGE Missing required bundle
org.eclipse.update.configurator_[3.1.100,4.0.0).
!SUBENTRY 1 org.eclipse.osgi 2 0 2008-10-17 15:41:18.645
!MESSAGE Bundle
reference:file:plugins\org.eclipse.update.core_3.2.201.R34x_ v20080714.jar
was not resolved.
!SUBENTRY 2 org.eclipse.update.core 2 0 2008-10-17 15:41:18.645
!MESSAGE Missing required bundle
org.eclipse.update.configurator_[3.1.0,4.0.0).
!SUBENTRY 1 org.eclipse.osgi 2 0 2008-10-17 15:41:18.645
!MESSAGE Bundle
reference:file:plugins/org.eclipse.update.ui_3.2.100.v200803 18.jar was not
resolved.
!SUBENTRY 2 org.eclipse.update.ui 2 0 2008-10-17 15:41:18.645
!MESSAGE Missing required bundle
org.eclipse.update.configurator_[3.1.0,4.0.0).
!SUBENTRY 1 org.eclipse.osgi 2 0 2008-10-17 15:41:18.645
!MESSAGE Bundle
reference:file:plugins/org.eclipse.core.runtime.compatibilit y_3.2.0.v20071008.jar
was not resolved.
!SUBENTRY 2 org.eclipse.core.runtime.compatibility 2 0 2008-10-17
15:41:18.645
!MESSAGE Missing required bundle
org.eclipse.update.configurator_[3.1.100,4.0.0).
!SUBENTRY 1 org.eclipse.osgi 2 0 2008-10-17 15:41:18.645
!MESSAGE Bundle
reference:file:plugins/org.eclipse.ui.ide.application_1.0.0. I20080603-2000.jar
was not resolved.
!SUBENTRY 2 org.eclipse.ui.ide.application 2 0 2008-10-17 15:41:18.645
!MESSAGE Missing required bundle
org.eclipse.update.configurator_[3.1.100,4.0.0).
!SUBENTRY 1 org.eclipse.osgi 2 0 2008-10-17 15:41:18.645
!MESSAGE Bundle
reference:file:plugins\org.eclipse.equinox.launcher.win32.wi n32.x86_1.0.101.R34x_v20080731\
was not resolved.
!SUBENTRY 2 org.eclipse.equinox.launcher.win32.win32.x86 2 0 2008-10-17
15:41:18.645
!MESSAGE Missing host org.eclipse.equinox.launcher_[1.0.0,1.1.0).

Our company has recently switched from Eclipse 3.2.2 to Eclipse 3.4.1. We
ship a rebranded version of Eclipse. It is composed of the base eclipse
platform as well as the emf runtime and gef runtime and the jet code gen
runtimes in addition to our plugins.

We change the config.ini file to rebrand the Eclipse platform. We also have
changed the .eclipseproduct to point to our product. Before the upgrade to
3.4.1 the config.ini looks like this:

osgi.launcherPath=.
org.eclipse.update.reconcile=false
osgi.framework=file\:plugins\\org.eclipse.osgi_3.4.0.v200806 05-1900.jar
osgi.splashPath =
platform:/base/../architect/eclipse/plugins/com.openedge.pdt .core
osgi.bundles=reference\:file\:org.eclipse.equinox.simpleconfigurator_1.0.0.v20080604.jar@1\:start
eclipse.product=com.openedge.pdt.core.product
osgi.instance.area.default=@user.home/workspace
eclipse.buildId=I20080617-2000
eclipse.p2.profile=PlatformProfile
eclipse.p2.data.area=@config.dir/../p2
eof=eof

After the upgrade to 3.4.1 The config.ini is rewritten and it looks like
this. Notice that the branding has been changed as well as the installed
product id

#This configuration file was written by:
org.eclipse.equinox.internal.frameworkadmin.equinox.EquinoxF wConfigFileParser
#Fri Oct 17 15:41:09 EDT 2008
osgi.launcherPath=.
org.eclipse.update.reconcile=false
eclipse.p2.profile=PlatformProfile
osgi.instance.area.default=@user.home/workspace
osgi.framework=file\:plugins\\org.eclipse.osgi_3.4.2.R34x_v2 0080826-1230.jar
eclipse.buildId=M20080911-1700
osgi.bundles=org.eclipse.equinox.common@2:start,org.eclipse.update.configurator@3:start,org.eclipse.core.runtime@start
org.eclipse.equinox.simpleconfigurator.configUrl=file\:org.e clipse.equinox.simpleconfigurator\\bundles.info
eclipse.product=org.eclipse.platform.ide
osgi.splashPath=platform\:/base/plugins/org.eclipse.platform
osgi.launcherIni=eclipse
eclipse.p2.data.area=@config.dir/../p2
eof=eof

If I change the line above to this:

osgi.bundles=org.eclipse.equinox.common@2:start,org.eclipse.update.configurator@3:start,org.eclipse.core.runtime@start

Then Eclipse will load fine. I then have to manually change the branding
and splash screen back to what they should be. This is fine for my, but for
our customers the loss of branding and fixing up the config.ini isn't
acceptable.
Previous Topic:Manage the updatesites
Next Topic:p2 is not picking up new versions of plugins
Goto Forum:
  


Current Time: Tue Sep 02 21:22:49 GMT 2014

Powered by FUDForum. Page generated in 0.06020 seconds