Community
Participate
Working Groups
When building a p2 repository that provisions RCP based products it's very convenient to rely on the org.eclipse.rcp feature. This feature lists all native fragments needed to make the repository contain what's needed for all supported platforms. The RCP feature however, also brings in a very large number of bundles that are unnecessary when building headless products so it's not really an option for that use case. Historically, it has been possible to use the org.eclipse.equinox.executable feature when building p2 repositories for headless products. In 3.7 that is no longer the case since this feature now contains dangling requirements. Since there seem to be strong opinions for keeping them (see bug 337334), the need arises for a new feature that defines the set of "supported" launchers, the same way the org.eclipse.rcp feature does. Perhaps the rcp feature could even be made to rely on this feature rather than repeating the launcher list again. Our builds are set up to have a minimum of redundancy and rely as much as possible on what is provided by the platform. This means that our builds are in a broken state at the moment. We are blocked by the fact that no feature exists that provides a canonical set of supported launchers. Hence the blocking status on this bugzilla.
We have workarounds so this is not blocking.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
