As exposed in JBIDE-15156, it's possible to successfully install parts of JBT into an Eclipse instance, but then have the JBT functionality missing due to missing undeclared runtime dependencies.

Tycho will catch missing build-time dependencies, but doesn't know about run-time dependencies.

Thus, to avoid JBIDE-15156 and similar (or undiscovered) problems in future, we ought to have Jenkins jobs that do this:

a) for a given matrix of Eclipse platforms (platform runtime binary, Classic, Java, JavaEE), perform headless install (unpack)

b) install a group of JBT features (eg., Server features, Forge features, GWT features, etc.), or install each update site category (core tools, web tools, mobile tools, cloud tools, general tools, reporting tools, etc.)

c) run SWTBot JUnit tests in that Eclipse instance to verify that UI and functionality are present and working as expected.