I've been looking into this and I suspect @myronmarston has run into this already with aslakhellesoy/aruba#27
The problem seems to lie in the assumption that Cucumber in general and Aruba in particular will run on all Ruby runtimes that RSpec supports.
Perhaps we should re-work the cukes to use a 'safe' runtime while allowing us to run rspec itself using a configurable interpreter. Something like
rake cucumber RSPEC_RUNTIME=/Users/sidu/.rvm/rubies/jruby-head/bin/ruby
A great deal has improved since the last time I looked at this - there's no problem running the cuke build on Jruby anymore (except that its horribly slow because of all the JVMs being created, so any CI server will have its CPU pegged).
All that needs to be done is to increase the aruba timeout to about 60s when on jruby and fix a couple of scenarios that are breaking because of the difference in backtraces from CRuby to JRuby. I should have a pull request in for this tomorrow.
Issue #344 - Increase Aruba's timeout to compensate for JVM startup
Increase Aruba's timeout to compensate for JVM startup
- Closes #344.
ci: add jruby to travis config