cucumber-jruby version clashes with cucumber-core

[notmattlucas]

Hi Samuel,

I've come across another potential issue which I've documented in the following example project :

https://github.com/lucas1000001/jruby-versioning-example

Basically I was getting some random compatibility issues when I tried to use a version of cucumber-jruby that did not match the cucumber-core version specified by the plugin's build script. I tried specifying a newer version of the cucumber-core dependency in my project, but unfortunately that didn't work either.

There are more details in the example project provided.

Anyway, I've logged just for completeness - I'll have a think and try and come up with a solution / workaround.

Thanks

Matt

[schuchert]

FYI, we had issues as well with this combination. We also had issues with the cucumber-jvm embedded in IntelliJ 12. In fact, the issue described in https://github.com/lucas1000001/jruby-versioning-example is a lot closer to the failure mode in IntelliJ than what we were getting.

When attempting to use the gradle cucumber plugin working with cucumber-jvm + JRuby, we'd run out of heap space (yes, we kept increasing heap space). We had other failures. I wonder if those were incorrect reporting of issues [I was not working on the problem at the time].

It turns out, we had JRuby versioning issues with whatever version of cucumber-jvm runs natively in IntelliJ as well.

When we switched to the java backend, it was all good. Our tests run fine at the command line using gradle as well as natively in intellij. In fact, we simply created a shell that uses the built-in JUnit runner so running our tests would work anywhere we can run JUnit (everywhere).

For now we are not using the JRuby back end. It'd be nice to allow the use of JRuby and the JRuby back end because we have some QA people who would like to write steps. As is, developers are writing the steps in Java.

[viphe]

The plugin recently allowed to override the versions of the Cucumber libs (basically, it is now build with a provided scope for those). Also, it now runs tests in a separate process.
I would need to give a shot at running with JRuby and/or from IntelliJ to validate if that gets rid of those issues.