That would be no problem since you can set the language explicitly with a
property like -Duser.language.
I know that Oracle database has such defaults when you install it, but you
can configure it afterwards to other timezones etc. This is not uncommon to
do so.
If you have a better idea of
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,
good code contributions are always welcomed !
2013/10/4 Hans Schwäbli bugs.need.love@gmail.com
I tried to use JBehave with German language.
Then I discovered that you have to configure a lot to achieve this.
This is because you have to create a Keywords object and set it into many
