Thank you Alex! It worked now. I had forgot to add the
jbehave-site-resources dependency.
But I get this XML error in Eclipse:
Plugin execution not covered by lifecycle configuration:
org.jbehave:jbehave-maven-plugin:4.0-beta-3:unpack-
view-resources (execution: unpack-view-resources, phase:
http://wiki.eclipse.org/M2E_plugin_execution_not_covered
On 07/10/2013 08:28, Hans Schwäbli wrote:
Thank you Alex! It worked now. I had forgot to add the
jbehave-site-resources dependency.
But I get this XML error in Eclipse:
Plugin execution not covered by lifecycle configuration:
I discovered that the GivenStories are not executed too. That worked
previously. Something is rotten in the state of Denmark.
2013/10/7 Hans Schwäbli bugs.need.love@gmail.com
I wonder why the StepMonitor I configured is not displayed anymore.
It used to work before I made some changes to
Thank you, this worked.
2013/10/7 Mauro Talevi mauro.tal...@aquilonia.org
http://wiki.eclipse.org/M2E_plugin_execution_not_covered
On 07/10/2013 08:28, Hans Schwäbli wrote:
Thank you Alex! It worked now. I had forgot to add the
jbehave-site-resources dependency.
But I get this XML
I created now a JIRA issue for this:
https://jira.codehaus.org/browse/JBEHAVE-945
2013/10/5 Mauro Talevi mauro.tal...@aquilonia.org
or good suggestions on how to achieve the goal.
The problem is striking a balance between flexibility and
configurability. We don't like setter and static
2013/10/5 Mauro Talevi mauro.tal...@aquilonia.org
We could make the language default to the platform locale, for example,
instead of the English locale.
No, please don't do that. This would mean that an identical setup would
run on a developer PC and stops working on the CI environment,
