JBehave provides the following modules, defined as POM artifacts:
| Module | Versions |
|---|---|
| jbehave-core | lookup |
| jbehave-groovy | lookup |
| jbehave-scala | lookup |
| jbehave-guice | lookup |
| jbehave-needle | lookup |
| jbehave-pico | lookup |
| jbehave-spring | lookup |
| jbehave-weld | lookup |
| jbehave-odf | lookup |
| jbehave-google | lookup |
| jbehave-rest | lookup |
| jbehave-maven-plugin | lookup |
| jbehave-distribution | lookup |
Once a version has been chosen, each artifact will declare the dependencies required.
Not all the required dependencies are found in Maven Central. The settings.xml defines the repositories for those not found in Maven Central. If you are running in a corporate environment, you may be using a Maven Repository Manager, such as Nexus, which may proxy the repositories behind a public open-source group.A POM artifact can be declared as dependency using different build systems:
Using Apache Maven, the dependencies are declared in the Maven pom.xml:
and the use of a custom settings.xml is declared via command line:
Maven dependencies are by default transitive, i.e. a top-level dependency will pull in all the dependencies it needs.To override a version of a specific dependency in the dependency tree, the most effective way is to use the dependency management of the POM.
Learn more about Maven dependency management from the Maven: The Complete Reference.
You can also retrieve the dependencies using tools that support the same repository format as Maven, such as Gradle, Grape, Ivy or sbt.