Community
Participate
Working Groups
Build Identifier: 20100218-1602 I ran into this problem when switching to P2, and the generated config.ini failed to use org.eclipse.equinox.simpleconfigurator. The problem seemed to be in the product file, which I had changed from "based on: plugins" to "... features", but the product file still listed the old plugins. Reproducible: Always Steps to Reproduce: 1. Create new product configuration, for example based on org.eclipse.platform.ide 2. In Overview, select "The product configuration is based on: plug-ins" 3. Under Dependencies, add some plugins 4. Save 5. Re-open *.product file, now select "The product configuration is based on: features" 6. Dependencies tab is empty. Maybe add a feature or not, doesn't matter 7. Save 8. Open *.product in text editor: It still lists the original <plugins> section .. and that plugins list seems to cause P2 to create a config.ini with osgi.bundles=...long list of plugins... Workaround: After manually removing the <plugins> section from the *.product in a text editor, so that it only contains features, P2 generates a proper config.ini and org.eclipse.equinox.simpleconfigurator setup. Unclear if this also points to a bug in P2, but the product editor is certainly misleading because it no longer displays the plugins when using feature-based configuration, even though they are still included in the *.product file.
This is intentional. It forgives the user to click on the feature/plugin toggle without losing the entire list of selected plugins. > .. and that plugins list seems to cause P2 to create a config.ini with > osgi.bundles=...long list of plugins... I have never seen this happen. Are you sure this is the case? If so, please re-open and re-target this bug.
