|Re: [p2-dev] Usage of 'useFeatures' attribute in p2 product files|
Thank you for your answer !
Well, fact is that I am creating the .product file manually J (in xml editor) and then run the Product Publisher application from the IDE, passing the file as an argument.
Still, the reason for introducing this restriction is entirely unclear to me. Furthermore, its logic extends from the PDE editors to the product publisher as well, as I pointed out below.
From a technical point of view, the p2 infrastructure is well prepared to handle such kind of “mixed” products and, if I am not wrong, the publisher needs only a small adjustment in its code to be able to define them (maybe at the cost of discarding the ‘useFeatures’ attribute which, of course, would be an incompatible change but I am sure that we can easily arrive at a more subtle solution). In that sense, this enforcement seems to be quite artificial and unnecessary to me. In fact, I would go as far as to classify it as a bug – there are no technical obstacles to install product IUs which list both features and plugins as their requirements but the infrastructure does not allow you to define them. Let me know if I am making a mistake here !
SAP Labs Bulgaria
How are you defining a product with *both* bundles and features? This behaviour is because the PDE Product Editors (which is the only "API" way to define product files) enforces this. That is, a product is made up of features XOR plugins.
FWIW, I agree, it would be nice to define a product with both features and plugins, but this isn't supported yet by the PDE.
On Thu, Aug 26, 2010 at 9:04 AM, Yousouf, Shenol <s.yousouf@xxxxxxx> wrote:
Recently, I had to build a product consisting of bundles only and was quite surprised to see that the described bundles were not included as requirements of the result product IU, published in the target p2 repository. After a debug session I found out that the “problem” was caused by the ‘useFeatures’ attribute in the .product file. It turns out that no bundles are considered as requirements of the product IU as long as the value of this attribute is “true”, even if there are such bundles described in the product file.
The interesting point for me here is the way this attribute’s value is interpreted (the programming logic can be found in org.eclipse.equinox.p2.publisher.eclipse.ProductAction.createRootAdvice(), as a reference):
- If ‘useFeatures’ is “true” then only the features described in the product file are included into the product; described bundles, if any, are ignored
- If ‘useFeatures’ is “false” then only the bundles described in the product file are included into the product; described features, if any, are ignored
- If the attribute is not defined in the .product file then its value is assumed to be “false” and we arrive at the case above
So it seems to me that there is no feasible way to publish both features and plugins in the same product. So far, I couldn’t find any meaningful documentation about the attribute’s semantics (aside from the javadoc for IProductDescriptor.useFeatures() which simply says that this flag “Specifies whether this product was built using features or not” ) to understand why it is so and whether it is intentional. Can anybody explain what is the rationale behind this behavior ?
Thanks and regards,
p2-dev mailing list
Back to the top