To try out cucumber-jruby, first build the full jar. Change directory to the root level and run:
Then, cd to jruby and run the features:
cd jruby jruby bin/cucumber-jvm --glue src/test/resources src/test/resources
cucumber-jruby.properties resource bundle
There is a resource bundle available to override a few environment variables for jruby. Specifically, the ability to set the GEM_PATH and to specify a version of ruby to build (1.8 or 1.9).
If the properties file is not present in the root of the classpath, any environment variables will operate as intended, otherwise the properties file will override the environment. Makes it much easier to run the features from within the IDE, and it encapsulates the settings in the project source tree easily.
Example cucumber-jruby.properties file
When filtered by the maven properties file, it will set Jruby's GEM_PATH to src/test/gems (expanded out to the full file system) so that Jruby can find any Gems you might be using.
The constructor of
JRubyBackend.java has the currently supported properties.