Added rubysl gem for Rubinius. Since Rbx 2.0+ extracts the Ruby Standard Library out into gems, and Bundler excludes them, this gem pulls them back in so calls expecting stdlib work right. This addition fixes that. Thanks goes to @brixen for the test and fix.
* Do not need to call as rbx-X.Y.Z to use latest stable RBX. Refined. Since RBX does not have a binary install available on Travis-CI, we can't simply add to the list, will require a custom from-src script.
MRI, JRuby, and RBX. All head versions of each are allowed to fail.
Removed JRuby-19mode from Allowed Failures since only JRuby-head should be allowed to fail as its 'head'. All others supporting 1.9.3 mode *must* pass.
RedCarpet is a Cext gem which JRuby disables by default. Goal is to completely remove, and ban any any/all Cext gems to keep JRuby native.
Options are for experimenting with ways to increase JRuby exec speeds.
Slowly, I'm removing all Cext gems as I find alternatives.
….yml * Travis is using RBX 2.0.0dev rather than rbx-1.2.4 or 2.0.0-rc1 for both the '2.0.0' tag, and the 'rbx-19mode' tag. Since there is no significant difference, and 2.0.0dev _and_ 2.0.0-rc1 default to 1.9 mode, removing the explicit 2.0.0 ruby test tag.
* Spoke with headius about the validity of testing against the different JDK versions such as Oracle vs. OpenJDK for JRuby, since DTF is purely Ruby code. Since there is no truly significant difference, testing using Oracle's JDK7 should be sufficient in most use cases of DTF. Should this, somehow, prove out to be an erroneous premise we can always add back the additional JDKs once Travis-CI also fixes the total ignoring of the 'exclude:' directive.
* To ensure that we are handling upgrade paths through the various Rubies, each implementation and its stepping version are included. To ensure we support new features and syntax changes going forward, the -head versions of each implementation were added. Ruby-2.0.0 was also added to ensure specific compatability.
…nored. * Following instructions at: http://about.travis-ci.org/docs/user/languages/ruby/#Testing-against-multiple-JDKs-(JRuby) and the example at: https://github.com/travis-ci/travis-support/blob/master/.travis.yml its *still* running multiple runs of each of the 1.9.x and rbx-19mode builds, one for each JDK being tested against for the JRuby builds. The proper excludes are in place, and the JDKs listed. Moving the jdk: entries in case ordering matters, and being placed before the matrix calls is blowing it. Just a guess.
* Added jruby-head and each of the 3 usable JDKs to the test matrix. This should suss out any differences or difficulties with JRuby. Since JRuby is newly supported, and Travis-CI doesn't have specific JRuby 1.7.1 support at the moment, I've added the JRuby builds to the allowed_failures:. This may need to be revisited should the matrix setup be incorrect.
* Documentation fix for version string of non-supported Ruby.
* Detailed the supported Ruby implementations for DTF * Fixed typos and whitespaces while in there.
* Travis-CI does not have JRuby 1.7.1, currently, in their images. This is being added as of this timestamp but is not currently in place. This change will be reverted as soon as it is live on Travis.
* This was largely copied from https://github.com/rails/rails/blob/3-2-stable/railties/lib/rails/application/configuration.rb#L110-L116
* Trying to rewrite database.yml to load the proper sqlite3 driver for either JRuby or MRI depending on which is running at the time. Keep getting ''mapping values not allowed here' errors.