Announcement (2017-05-07): www.ruby-forum.com is now read-only since I
unfortunately do not have the time to support and maintain the forum any
more. Please see rubyonrails.org/community and ruby-lang.org/en/community
for other Rails- und Ruby-related community platforms.

Hi Ashbb,
We found a similar issue when compiling with warbler when invoking with
jruby-complete.jar. The command line arguments are not propagated to the
process that invokes jrubyc, so it always runs in the default (1.8)
mode.
We patched warbler to send --1.9 to jrubyc when invoked in 1.9 mode, so
you
might need to do the same thing for rawr. I see it uses a slightly
different mechanism for calling jrubyc, but it looks like that method
can
also take additional arguments, like the --1.9 flag (in the
file lib/rawr/jruby_batch_compiler.rb).
I think that jruby-1.7 will default to 1.9 mode, but then the people
needing 1.8 mode will encounter the same grief :(
Regards,
Michael

Hi Eric,
Thank you for the information. Sorry for this late reply.
I tried your suggestion, but umm,... got the same error...
But I tried the following. It worked!
C:\tmp\hello>java -Djruby.compat.version=RUBY1_9 -jar
package\jar\lib\java\jruby-complete.jar main.rb
{:a=>1, :b=>2}
Thanks to your information, I got a solution, not using rawr, though.
:-P
ashbb

Hi Michael,
Thank you for the reply. Sorry for this late reply.
> We patched warbler to send --1.9 to jrubyc when invoked in 1.9 mode, so> you might need to do the same thing for rawr.
You are right.
I'd like to improve rawr to run in 1.9 mode.
But I've no skill. :(
> I think that jruby-1.7 will default to 1.9 mode
Wow, cool!
> but then the people needing 1.8 mode will encounter the same grief :(
hahaha. True!
But can't wait to use jruby-1.7!!
ashbb