'MyTool integration with XYZ', which have mandatory requirements to the optional content and hence cause the installation if the user chooses to install the feature. Instead, you should offer additional features, e.g. Note: Optional greedy dependencies should be avoided, because they don't really give the users of your bundle the choice whether they want the optional content installed or not (see bug 247099).

an optional dependency shall be satisfied during installation whenever possible, the dependency can be annotated with an additional directive: resolution:=optional x-installation:=greedy. At runtime, the optional requirement will only be satisfied, if there was some other, mandatory requirement to the provider, e.g. the optional run-time dependency will not cause any additional installation. Since Juno M1, an optional non-greedy dependency is generated, i.e.the optionally required bundle or package was installed whenever possible. In Indigo and earlier, an optional greedy dependency was generated, i.e.an resolution:=optional directive in Require-Bundle or ImportPackage headers) are interpreted in the following way: The BundlesAction generates the p2 metadata for OSGi bundles. This section describes the behaviour of some of these actions. The publisher applications and Ant tasks each execute a set of publisher actions. 3.2 Features and Bundles Publisher Task.2.2 Features And Bundles Publisher Application.

Eclipse how to install equinox p2 rpc