Community
Participate
Working Groups
Build ID: I20081211-1908 Steps To Reproduce: 1. Make a clean Eclipse install read-only to force per-user configuration data. 2. Launch Eclipse. Use the P2 update manager to install a plugin (say, subclipse). Notice that the plugin was installed in the per-user area. Restart Eclipse. 3. Notice that the new plugin is not active (the red cross in the 'Manage Configuration' dialog) and that the P2 update manager is gone, replaced by the classic update manager. More information: In this state, the following error is observed in the error log: org.osgi.framework.BundleException: The bundle could not be resolved. Reason: Missing Constraint: Require-Bundle: org.eclipse.equinox.p2.touchpoint.eclipse; bundle-version="1.0.0" Could this be similar to Bug 231349? If, after this happens, -clean is added to the startup options, Eclipse will fail to launch with this error: !ENTRY org.eclipse.osgi 4 0 2008-12-15 10:07:59.784 !MESSAGE Bundle reference:file:org.eclipse.equinox.launcher_1.0.200.v20081201-1815.jarreference:file:org.eclipse.equinox.launcher.carbon.macosx_1.0.200.v20081124-1800/reference:file:org.eclipse.update.configurator_3.2.300.v20081127.jarreference:file:org.eclipse.core.runtime_3.5.0.v20081110.jar@:startreference:file:org.eclipse.equinox.p2.reconciler.dropins_1.0.100.v20081210-0057.jar@:startreference:file:org.eclipse.equinox.simpleconfigurator_1.0.100.v20081210-0003.jar@1:start not found. !ENTRY org.eclipse.osgi 4 0 2008-12-15 10:07:59.796 !MESSAGE Application error !STACK 1 java.lang.IllegalStateException: Unable to acquire application service. Ensure that the org.eclipse.core.runtime bundle is resolved and started (see config.ini). at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:74)
Do you know if this was working on 3.4? I believe it was not. *** This bug has been marked as a duplicate of bug 258365 ***
(In reply to comment #1) > Do you know if this was working on 3.4? I believe it was not. > > *** This bug has been marked as a duplicate of bug 258365 *** Hmm. Interesting. This may be a regression of Bug 231349, because this was working at one point in time. I tried this with three different builds I happened to have around: 3.4.0 I20080617-2000 -- Works 3.4.1 M20080911-1700 -- Fails 3.5.0 M3 I20081030-1917 -- Fails It looks like somewhere between 20080617 and 20080911 this regressed.
*sigh*, thx
