Community
Participate
Working Groups
build I20050217-1602 - create a new RCP app launch config - make sure the config location is not used by any existing launch config - specify @none as the workspace location (this may be irrelevant, but it's what I was testing at the time) - select the IDE product - launch - exit - change the product to the browser product (in org.eclipse.ui.examples.rcp.browser) - in the plugins tab, choose only org.eclipse.ui.examples.rcp.browser and its prerequisites - launch - it gets lots of errors, trying to process the IDE plugins (I have lots of plugin projects loaded in my workspace) - it should not be seeing these plugins The workaround is to check "Clear the configuration area before launching"
just verified that the config.ini generated by PDE is correct every time and updated with the correct product. It's a runtime problem.
Can you attach a log file?
Created attachment 18111 [details] 1108753987071.log Here one from mine reproducing the problem.
Created attachment 18112 [details] config.ini And the corresponding config.ini that was used
I am able to reproduce. The problem is caused by switching to a configuration that does not use update.configurator to install bundles. When you switch to an RCP application all of the bundles of the application are put onto the osgi.bundles list. EclipseStarter tries to make the set of installed bundles match the list in osgi.bundles. The problem is we do not process any bundles not installed by EclipseStarter (i.e. bundles with locations starting with initial@). As a result we uninstall update.configurator because it is no longer in the osgi.bundles list and we try to install the rest of the bundles on the list. But the bundles are already installed under "update@" locations so we fail to install these bundles. The rest of the errors in the log are unresolve errors that resulted from update.configurator being uninstalled. EclipseStarter would have to become a lot smarter to prevent such errors from occurring. The basic problem here is switching from an environment controlled by update.configurator to an environment only controled by the list of bundles in the osgi.bundles. Should we attempt to solve this? or just state that it is not supported without clearing your configuration area?
Given the time line, this should be a readme.
README entry from Tom. McQ, please add to the README file. Thanks. We'll leave this bug open as there is still work to do for 3.2. -------------------- Configuration can become invalid when removing org.eclipse.update.configurator When launching an Eclipse Application from within the Eclipse IDE it is possible to select the set of plug-ins that are included in the Eclipse Application. Removing the org.eclipse.update.configurator plug-in from the set of plug-ins to an existing configuration can cause the configuration to become invalid. This can result in extra plug-ins installed in the target application that are not resolved. To work around this, after the org.eclipse.update.configurator plug-in has been removed, the target configuration area should be cleared before launching. (bug 85835)
Created bug 101446 to address adding this to the README. Clearing the target milestone of this bug because there is real work to do.
Removed "[doc]" tag from the summary - corresponding doc bug was fixed. Should this bug be closed as "won't fix"? The last update is two years ago.
This is no longer relevant now that update.configurator is obsolete.
