zest dependencies missing

[Bananeweizen]

The Usus update site does not contain the necessary zest dependencies. Therefore an installation only works without flaws on Eclipse systems where zest was packaged or already installed by another plugin (e.g. it does not install on my 4.2 SDK).

If I remember right, there is a checkbox in the update site editor to include such dependencies, which should solve this.

[marcphilipp]

That is actually on purpose since the Zest version is resolved
automatically using the Eclipse release update site that corresponds
with the installation. I've never had problems with this setup.

Did you deactivate the Eclipse release update site in your installation?

[Bananeweizen]

That can easily break for different reasons:

First, the P2 tooling must actually contact the Eclipse update site. Using the P2 update dialog "Contact all update sites" must be checked (and I'm not sure if it is by default). When using other installation routines (e.g. File->Import->Install->From file or the P2 CLI application or...), those also must be forced to check all update sites somehow.

Next, the Eclipse update site must be reachable. In company environments (like mine) lots of update sites cannot be resolved due to a very restrictive proxy (although admittedly I can access the main Eclipse update site). If someone mirrors your feature to another update site using the P2 mirroring capabilities (to avoid relying on update sites in the Internet), then your feature is incomplete on such an isolated mirror.

Can't you have zest as so called "included feature" in your own feature definition? That way it would be available during installation if needed. And it would still allow updating the zest component using the main update site, as far as I understood. Or am I missing something there, maybe?

[marcphilipp]

Since "Contact all update sites" is checked by default, it works for
"most" people out of the box. ;-)

I didn't want to get into building release-specific update sites
because of new Zest releases. Therfore, I decided not to include it in
our update site.

Feel free to look into including it if you care enough. The update
site is build using Tycho BTW.