Re: [ease-dev] Advice on packaging EASE

[Geneviève Bastien <gbastien+lttng@xxxxxxxxxxxx>]

Hi Christian,


On 5/8/19 11:35 AM, Christian Pontesegger wrote:
>> We have a product (TraceCompass), to which we're adding optional EASE
>> support. We'd like our users to be able to install our EASE modules,
>> along with a script language of their choice, in one single install,
>> using our p2 discovery update site.
>>
>> [...] Ideally, we'd like p2 to be able to resolve
>> the
>> correct dependencies and get those packages from where they reside.
>>
> With p2 you can use associated update sites. This means that your
> update site can define references to other p2 sites which will
> automatically be used to resolve features during an install. See
> https://git.eclipse.org/c/ease/org.eclipse.ease.core.git/tree/releng/or
> g.eclipse.ease.releng.p2/pom.xml
>
> to check out how we use this for external EASE engines. This might help
> you to avoid mirroring EASE stuff into your p2 repos.

Thanks for this info, the pom.xml approach works as we hoped!

Geneviève