Community
Participate
Working Groups
Our equinix.ds can now be exchanged based on Bug 481449. Unfortunately PDE does not yet consider the Provide/Require-Capability from OSGi in its dependency resolution / validation. For example if I define a new product and forget to include equinix.ds, the "Validate" button in the product does not find any problem. This should get fixed.
First, I don't think it is now possible to exchange the ds implementation for Eclipse RCP applications. I tried this with a very simple application and failed. The reason is the usage of Require-Bundle of org.eclipse.osgi.services in the platform bundles. I opened Bug 496557 for this. Second, I think your ticket is related to Bug 313553. p2 does not support OSGi capabilities, therefore the p2 resolver doesn't check. BTW, is this ticket about the launch configuration or the product configuration? I just checked it with a launch configuration and there I get the validation error if I forget to add the ds bundle. Oh, and is the version really 4.2?
I think that the problem that I'm facing with PDE is related to this issue. When I try to launch equinox using internal launcher configuration UI and there are any bundle selected that is requiring a Capability then a validation error (Missing Constraint: Require-Capability: osgi.service;..." will be detected, even if the bundle providing such capability is already on the current target platform. It worth to tell that the problem occurs only in PDE validation before run. Equinox resolves all capabilities requirement properly once it is running.
Switching to a OSGi State based dependency calculation in the linked bug should also fix this issue. *** This bug has been marked as a duplicate of bug 539637 ***
