RVM defines GEM_HOME and JRuby installs it's development gems in the wrong place. The install-dev-gems ant task now proactively defines GEM_HOME to reference JRuby's gem home for 1.8 gems. Having GEM_HOME reference another Ruby is still a problem for JRuby, this patch just fixes the ant task.
…t to bind straight through.
* Methods that take block are bound now (still no call sites that pass block though) * Simpler logic for permuting incoming arguments into place * Easier path to getting other target forms binding (only forms that take ThreadContext bind now)
…r in diffs
JRuby uses the patched version of securerandom.rb for both 1.8 and 1.9 which utilizes java.security.SecureRandom. Using nextInt causes this RangeError for bit number so introduce CRuby's byte operation implementation.
A second thread requiring a file currently being required should block and wait for that require to complete. My fix for JRUBY-5779 changed the locking mechanism so I added a regression spec and fixed it.
…gs of pre/post wrappers for native.
Call addLoadedFeature(feature) after the feature is loaded. Existing add-first logic worked for avoiding circular require so I added new circular require detection logic at LoadService#require(). At this moment, this change causes lots of constant redifinition warnings for rubygems under 1.9 mode. Plus, builtin/javasupport looks to have circular require in it.
…ity. Pointed out and initial patch by Chung Shin Yee <email@example.com>