From 3.0 to 3.1

The Story Maps view has been added to the Story Reports view. As such, the default output directory has been renamed from jbehave-reports to jbehave. The main index view in target/jbehave/view/index.html now links to both the maps and reports views (view/maps.html and view/reports.html, respectively). Currently, it assumes that both views are generated and there is no check on whether these views exist or not. An upcoming enhancement will determine which views have actually been generated and enabled the links accordingly.

Operationally, users should change the target view directory of the jbehave view resources to target/jbehave/view. Maven users can use the new unpack-view-resources goal which will derive the view directory from the configured Embedder.

It is also recommended to use the latest released version 3.1.1 of the jbehave-site-resources.zip, which uses a SyntaxHighlighter BDD brush to decorate all plain-text output.

From 2.x to 3.0

JBehave 3.x is an evolution of 2.x, based on the experience using it in commercial projects. With the benefit of this experience, we feel that the overall design stood well the wear and tear, but there were areas which called for improvements that required to break backward compatibility.

From the textual stories point of view, these are almost completely backward compatible. The only exceptions being:

From the Java point of view, significant changes have occurred, but only in the configuration of the running of the stories. The Steps classes, which is where most users' efforts will have gone into can be used without change in JBehave 3.

On the configuration side, the main changes are:

Next?

JBehave development has been example-driven and the examples illustrate all the features, migrated from 2.x or new in 3.x. Be sure check out the running examples, as it's the quickest and most instructive way to get up to speed with the changes outlined above.