The following section describes where to find the relevant JARs / artifacts to use the API. The provided API has a miminum required runtime environment of Java 6.
In general the usage of the client API falls apart into three categories of JARs / maven artifacts / OSGi bundles:
Each project requires dependencies to all of the toolkit neutral parts of the API:
org.eclipse.jubula.client.api
org.eclipse.jubula.client.api.commands
org.eclipse.jubula.toolkit.api
org.eclipse.jubula.tools
org.eclipse.jubula.communication
Each project requires dependencies to indiviual parts of the toolkit specific elements dependent from the used toolkit of the API:
org.eclipse.jubula.toolkit.base.api
org.eclipse.jubula.toolkit.concrete.api
org.eclipse.jubula.toolkit.javafx.api
org.eclipse.jubula.toolkit.swt.api
org.eclipse.jubula.toolkit...TOOLKIT_ID...api
Please keep in mind that toolkits are derived from each other. So if you're e.g. setting up a JavaFX projects it is also necessary to include the direct dependency to the specific toolkit artifact "org.eclipse.jubula.toolkit.javafx.api" itself as well as the toolkits its based upon: "org.eclipse.jubula.toolkit.concrete.api" and its base "org.eclipse.jubula.toolkit.base.api".
Each project also requires dependencies to all of the 3rd party dependencies of the API:
Apache Commons Lang 2.6
Apache Commons Codec 1.6
SLF4j API
XStream 1.3.1
xmlpull 1.1.3.4a
You can find the artifacts in different shapes (plain JAR and maven artifact) within the <ITEInstallationFolder>/development/api folder. To define OSGi dependencies to the API artifacts you can simply include the <ITEInstallationFolder>/development/org.eclipse.jubula.repo.zip in your target platform (definition) and define a dependency to the "Jubula Functional Testing - API Core"-feature.
A list of changes which happened over time in the API is located here.