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 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.
Please raise a JIRA issue for this.
Cheers
On 04/10/2013 14:49, Cristiano Gavião wrote:
good code contributions are always welcomed !
2013/10/4 Hans Schwäbli <bugs.need.love....@gmail.com
<mailto: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 other objects. See
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.
Furthermore you need to configure that in the Eclipse plugin.
I think this could be made much simpler. Can you make setting a
language simpler please (suggestion)?
The Eclipse plugin could detect the language of the story files
automatically by default for instance.
And there could be made a JBehave utility method (and maintained
in the JBehave Core project) which sets the language into all
required objects. Or it could even auto-detect the language
(according to the translations shipped which JBehave) by default.
This is just a suggestion.
--
"Tudo vale a pena se a alma não é pequena..."
