The JRuby community is pleased to announce the release of JRuby 1.7.18
- Homepage: http://www.jruby.org/
- Download: Downloads — JRuby.org
JRuby 1.7.18 is our twenty-first update release since JRuby 1.7.0. The
primary goal of 1.7 point releases is to fill out any missing
compatibility
issues with Ruby 1.9.3.
The goal of this release was to give a quick turnaround for bug
reporters
of 1.7.17. We wanted to get one more solid release out before the
holidays…
Highlights:
- 20 issues fixed for 1.7.18
- non-ASCII Symbols now have their proper encoding
- fixed a couple of regressions from native crypt() landing
- update stdlib to match MRI (C Ruby) patch level 551
Github Issues resolved for 1.7.18
#2342 - Java::JavaLang::NullPointerException:
org.jruby.RubyString.crypt(RubyString.java:2660)
#2331 - File.realpath treats absolute “classpath:/” paths as
relative
paths
#2327 - added String#b method
#2316 - I/O calls do not invalidate String#ascii_only? cache
#2310 - ArgumentError: “+HH:MM” or “-HH:MM” expected for utc_offset
#2307 - ConstantCompilationTest.testContainerCompilation regression
#2304 - Unable to use JRuby with google app engine due to use of
sun.misc.Unsafe
#2302 - Update JRuby 1.7.x to latest PL and default gems
#2301 - unable to get value of object’s fields in RubyMine debugger
#2298 - Open3.capture3 still broken in JRuby 1.7.17
#2297 - File.executable? raises an exception if the file_path is
non-existent and native disabled
#2296 - NullPointerException with JRuby 1.7.17 running rspec &
simplecov in debug mode
#2295 - Regexp.union [] gives wrong result in ruby 1.8 mode
#2294 - String#crypt fails on Windows
#2291 - Dir[] fails if path does not exist instead of returning nil
#2259 - File.basename can return a string with a different encoding
than the input
#2172 - Symbols need to support UTF-8 names
#2048 - Stat of an empty resource does not generate proper
Exception.
#1941 - Symlinks in load path should remain unexpanded in
LOADED_FEATURES
#1237 - jffi*.tmp files remain in %TMP% folder