[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [p2-dev] Product definition as extension of another product
- From: Hugues Malphettes <hmalphettes@xxxxxxxxxxx>
- Date: Thu, 2 Sep 2010 08:16:27 -0700
- Delivered-to: firstname.lastname@example.org
I was facing a similar situation: core.product,
core-with-extras.product where core-with-extras.product is core, some
new features and a couple bundles to start automatically.
The best solution I found so far consists of eliminating the second 2
I re-factored this setup so that the "extras" are all described via a feature.
The extra bundles to be started are now enabled via a bit of glue code
added to the core.product.
This code is able to detect the extra bundles and start them early enough.
I hope this helps.
On Thu, Sep 2, 2010 at 12:23 AM, Yousouf, Shenol <s.yousouf@xxxxxxx> wrote:
> Hi all,
> The following scenario sounds simple but I cannot find an elegant solution
> to implement it:
> I have a product A and now I need a product B which extends product A in the
> sense that it includes product A’s IUs + some IUs of its own. However, it is
> well known that a p2 product definition can include only features xor
> bundles but cannot point to another product. (correct me if I am wrong)
> The obvious solution is to list product A’s features in product B’s
> definition. The disadvantage here is that any update in product A must be
> manually reflected into product B’s definition. Could you point me to a more
> clean (build/publishing) procedure which will map changes in A automatically
> to B ? You can also assume that A and B should be published into two
> different p2 repositories. However, if this complicates the scenario too
> much, we can resort to the usage of one p2 repository only.
> Thanks in advance for any hints you can give me !
> Best regards,
> Shenol Yousouf
> SAP Labs Bulgaria
> p2-dev mailing list