New Jnario release 0.7.1

62 views
Skip to first unread message

Sebastian Benz

unread,
Jan 12, 2014, 4:33:14 PM1/12/14
to jna...@googlegroups.com
Hello everyone,

there is a new Jnario release 0.7.1 available with support for Xtend 2.5. You can install it via the update site  or maven central. 

Regards,

Sebastian

Typhoon Storm

unread,
Jan 13, 2014, 5:11:47 AM1/13/14
to jna...@googlegroups.com
What a good news! Thanks!

Jeremy

unread,
Feb 10, 2014, 6:58:40 AM2/10/14
to jna...@googlegroups.com
Hi Seb,

I've just upgraded to the latest release (different project work for the last two months), and found that it's not working in my Eclipse. I'm using jnario 0.7.1 and xtend 2.5.1

I've attached the stacktraces I get in Eclipse for this problem..
jnario.txt

Jeremy

unread,
Feb 10, 2014, 7:01:11 AM2/10/14
to jna...@googlegroups.com
Additionally I've downloaded the latest version of Eclipse Kepler and used a fresh workspace, then installed jnario and am having the same problems in a new project.

Sebastian Benz

unread,
Feb 10, 2014, 7:23:21 AM2/10/14
to jna...@googlegroups.com
Hello,

Xtend 2.5.1 introduced some breaking changes. I will release Jnario 0.7.2 in the next days.

Sebastian


On Mon, Feb 10, 2014 at 1:01 PM, Jeremy <jeremyl...@gmail.com> wrote:
Additionally I've downloaded the latest version of Eclipse Kepler and used a fresh workspace, then installed jnario and am having the same problems in a new project.

--
You received this message because you are subscribed to the Google Groups "Jnario" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jnario+un...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Jeremy

unread,
Feb 10, 2014, 7:37:41 AM2/10/14
to jna...@googlegroups.com
So I've just found :) I've managed to get Eclipse to revert down to xtend 2.5.0 and things seem to be working now.

Jeremy

unread,
Feb 10, 2014, 10:28:26 AM2/10/14
to jna...@googlegroups.com
I've noted a validation error is happening with the Should Be operator - if I clean my project and recompile, many instances of "should be" (see snippet one) are throwing invalid number of arguments exceptions (see snippet two). I'm currently ignoring the errors as touching one of the feature files seems to make the error resolve and go away.

snippet one:

        Given I am on the A to Z subjects page
                aToZPage.get(true)       
        When I select "ABC" in the subject category list
               categoriesPage = aToZPage.selectSubject(args.first)
        Then "ABC" subject category should be active
                categoriesPage.checkSubject(args.first) should be true

snippet two:
Invalid number of arguments. The method should_be(T, Function1<T, Boolean>) is not applicable for the arguments (IntegratedSubjectSearchFeatureCheckUserCanSelectASubjectFromSubjectList)   

Jeremy

unread,
Feb 10, 2014, 10:31:42 AM2/10/14
to jna...@googlegroups.com
And the maven compiler won't work either - you get a "[ERROR] Don't resolve expressions during indexing!" exception if you attempt to re-use a step (even within the original file).

You can replicate with a feature similar to the below (usage "mvn clean test-compile", if you only have the first scenario in the feature, the compile works. When you have the second one, mapped to the steps from the first, it breaks):

Feature: Test

    Scenario: Test something
            Calculator calculator
            int result
        Given A calendar
            calculator = new Calculator
        When I add "2" and "3"
            result = calculator.Add(args.first.toInt, args.second.toInt)
        Then I should get "5"
            result should be args.first.toInt
           
    Scenario: Test something else
   
        Given A calendar
        When I add "3" and "10"
        Then I should get "15"

Sebastian Benz

unread,
Feb 12, 2014, 3:58:25 PM2/12/14
to jna...@googlegroups.com
Hello Jeremy,

I couldn't reproduce you problem. Could you please file a bug at github with a concrete example.

Thanks,

Sebastian


--

Jeremy

unread,
Feb 14, 2014, 11:45:43 AM2/14/14
to jna...@googlegroups.com
No problem.

Maven is able to do the build, it's just it dumps out a large amount of errors, I'll zip up a small test project for you.
Reply all
Reply to author
Forward
0 new messages