[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [ease-dev] Advice on packaging EASE
|
Hi Bastien,
>
> 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.
> Anyone has experience with that? How do you get users to install the
> EASE features with language support without prior knowledge and what
> to
> install from where?
>
For selection of the right engine + components you either need your
users to pick the right stuff or you do something similar to what SVN
does: on the first startup it opens a popup asking which SVN connector
should be used. After selection it gets installed into the running
eclipse application. You could provide a similar helper for your users,
providing a selection of available engines.
HTH
Christian
