I’m was trying to play around with jar-ing up a project in warbler using
JRuby 1.7, but ran across errors starting up a warble “compiled” jar,
with
my .rb classes compiled. Not sure if this is related to 1.9.2 -> 1.9.3,
or
if this is something new with JRuby 1.7, but it keeps throwing errors
trying to require a compiled class.
I inspected a bit more - I unzipped the jar and tried to require a
single
compiled class in irb:
bporterfield@ ~/require_problem$ ruby -v
jruby 1.7.0.dev (ruby-1.9.3-p139) (2012-03-29 4972b84) (Java HotSpot™
64-Bit Server VM 1.7.0_04-ea) [darwin-amd64-java]
bporterfield@ ~/require_problem$ irb
require ‘jruby-head :001 > require ‘config.class’
LoadError: no such file to load – config.class
from org/jruby/RubyKernel.java:991:in require' from /Users/bporterfield/.rvm/rubies/jruby-head/lib/ruby/shared/rubygems/custom_require.rb:36:inrequire’
from (irb):1:in evaluate' from org/jruby/RubyKernel.java:1037:ineval’
from org/jruby/RubyKernel.java:1353:in loop' from org/jruby/RubyKernel.java:1146:incatch’
from org/jruby/RubyKernel.java:1146:in catch' from /Users/bporterfield/.rvm/rubies/jruby-head/bin/irb:17:in(root)’
jruby-head :002 > load ‘config.class’
=> true
Warbler auto-creates .rb stubs when compiling that look like: require
FILE.sub(/.rb$/, ‘.class’) - I tried changing stubs to
‘load FILE.sub(/.rb$/, ‘.class’)’ and the app seemed to load
properly.
Is this an expected change?