The JBehave Core requires the following dependencies to be in the classpath:
All dependencies are provided in the lib directory of binary distribution from the download page.
Attention: if you use junit.jar, be aware that from version 4.4 it comes bundled bundled with a copy of Hamcrest API, so you may experience unpredictable behaviours based on the relative position of the jars in the classpath. It is advisable to use the junit-dep.jar which is identitical, except that is come unbundled and any dependencies must be declared.
Note: JBehave Core is agnostic of any build tools, althought it does contain an optional dependency on the ant.jar for the implementaion of the StoryClassNameFinder. This is a utilily class which is used only by the JBehave Ant and JBehave Maven Plugin modules.
The JBehave Pico module requires the following dependencies (and their transitive dependencies) to be in the classpath (in addition to Core and its dependencies):
The JBehave Spring module requires the following dependencies (and their transitive dependencies) to be in the classpath (in addition to Core and its dependencies):
The JBehave Ant module requires the following dependencies to be in the classpath (in addition to Core and its dependencies):
The JBehave Maven Plugin module requires the following dependencies to be in the classpath (in addition to Core and its dependencies):