the Gem.path changed from 1.7.5 to append the jruby internal path at the end. which matches MRI (as far I can tell)

from 1.7.5 onwards the internal "default" gems get preference over the gems installed somewhere else. 1.7.12-SNAPSHOT/9000.dev does even ignore those installed altogether and only loads the internal ones. same did 1.7.9,1.7.8,1.7.6

1.7.11 sees the jruby-openssl gem and use it.

but jruby-openssl installed outside of jruby is version 0.9.4 and the default gem is version 0.9.3. for bouncy-castle-java gem it 1.7.5 or newer always loads the internal default gems.

https://gist.github.com/mkristian/9599309

however the given Gem.path indicates that the given GEM_PATH is first in the path and I would expect those gems get preference to the gems further behind in the Gem.path - as 1.7.4 does it.

if I add a gem 'jruby-openssl' in the beginning of the test script the situation is slightly different.

altogether I would expect with or without the extra gem 'jruby-openssl' that the externally installed gems have preference as the Gem.path indicates (as 1.7.4 did it) and those krypt gems are used then they are loaded gems, as 1.7.11 does show but 1.7.12-SNAPSHOT not anymore.

it is not clear what is the right behaviour should be.