Details
-
Type:
Improvement
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Number of attachments :
Description
In order to configure the language of the story files the JBehave user has to do a lot or otherwise JBehave won't work correctly.
This is because you have to create a Keywords object and set it into many other objects:
http://jbehave.org/reference/stable/stories-in-your-language.html
If you forget to set the Keyword object into one of the other objects, then it does not work correctly, tests fail. Or if JBehave is changed in a future version, your language configuration might not work anymore.
The problem is striking a balance between flexibility and configurability. We don't like setter and static injection. We prefer CDI. The issue here is how to make this easier to configure and what is the sensible default.
We could make the language default to the platform locale, for example, instead of the English locale.
This default could be changed (if needed) by a dedicated JBehave property for configuring the story language. This seems to be more flexible than having to change the platform locale or passing -Duser.language to the java process.
The origin for this issue is a mailing list discussion:
http://www.mail-archive.com/user@jbehave.codehaus.org/msg01954.html
