Would you mind putting this on github? It's much easier to provide patches and see diffs.

On 03/06/2015 07:25, Attila Franczen wrote:
Hello Mauro,

Thank you for taking the time to help me. A really appreciate it. I have attached a working sample, pom included this time


2015-06-02 23:23 GMT+02:00 Mauro Talevi <[email protected] <mailto:[email protected]>>:

    Hi,

    it would seem that your Maven classpath does not include the
    keyword properties file.

    Since your src zip does not include the Maven pom, it's not
    possible to say why.

    Can you please provide a fully functional example, executable via
    Maven?

    Cheers

    On 02/06/2015 12:35, Attila Franczen wrote:
    Hello!

    I started to experiment with jbehave a couple of days ago, and
    already I'm facing issues I can't resolve.
    Here is one of them, which is a major showstopper, because it
    prevents me to use this tool in my native language. This is what
    I did:
    1. Created a new jbehave project from jbehave-simple-archetype
    http://jbehave.org/reference/stable/archetypes.html
    2. I added a story, added a configuration, added basic steps. Ran
    it. Everything was fine (well, not quite, but that's another issue).
    3. Created a property file, with localized keywords. Placed it
    under src/main/resources/i18n/keywords_hu_Hu.properties, renamed
    my story file to match the given ending (.sztori instead of
    .story), edited the given/when/then blocks to match the
    translated ones, and of course edited the configuration file to
    pick up my custom keywords file.

    According to this:
    http://jbehave.org/reference/stable/stories-in-your-language.html
    The naming and placing convention of the file should be:
    "Write a properties bundle containing the following keywords and
    save it as *i18n/keywords_xx.properties*. E.g. for Italian
    *i18n/keywords_it.properties*:"
    So this is what I did, as descriped in step 3 above.

    Now, running the story from the IDE works just fine

    But running it from console with either mvn clean install, or mvn
    clean integration-test gives me the following error:

    [ERROR] Failed to execute goal
    org.jbehave:jbehave-maven-plugin:4.0-beta-11:run-stories-as-embeddables
    (embeddable-stories) on project memese-jbehave: Failed to run
    stories as embeddables: Failure in running embeddable:
    hu.tigra.test.SomeSztori: Resource bundle i18n/keyword
    s not found for locale hu_HU in classLoader
    ClassRealm[plugin>org.jbehave:jbehave-maven-plugin:4.0-beta-11,
    parent: sun.misc.Launcher$AppClassLoader@b2929b2]: Can't find
    bundle for base name i18n/keywords, locale hu_HU -> [Help 1]

    Sure, I've also tried placing the keywords file right next to the
    other files, and use the other constructor of LocalizedKeywords
    class, but nothing worked.

    What am I missing? Please help. (Sample source code attached.)

    Attila
-- You received this message because you are subscribed to the
    Google Groups "JBehave User" group.
    To unsubscribe from this group and stop receiving emails from it,
    send an email to [email protected]
    <mailto:[email protected]>.
    To post to this group, send email to
    [email protected] <mailto:[email protected]>.
    To view this discussion on the web, visit
    
https://groups.google.com/d/msgid/jbehave-user/5663708f-3713-4fb9-a9c8-4051a8b2918a%40googlegroups.com
    
<https://groups.google.com/d/msgid/jbehave-user/5663708f-3713-4fb9-a9c8-4051a8b2918a%40googlegroups.com?utm_medium=email&utm_source=footer>.
    For more options, visit https://groups.google.com/d/optout.



--
You received this message because you are subscribed to the Google Groups "JBehave 
User" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send an email to [email protected].
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/jbehave-user/556EC018.7060308%40aquilonia.org.
For more options, visit https://groups.google.com/d/optout.

Reply via email to