ninjudd/drip

JRuby won't run on the second invocation

Closed this issue · 4 comments

iconara commented

I tried drip with JRuby, this is what happens:

% drip -cp $MY_RUBY_HOME/lib/jruby.jar org.jruby.Main -v
jruby 1.6.7 (ruby-1.8.7-p357) (2012-02-22 3e82bc8) (Java HotSpot(TM) 64-Bit Server VM 1.7.0_04) [darwin-x86_64-java]
% drip -cp $MY_RUBY_HOME/lib/jruby.jar org.jruby.Main -v
Exception in thread "main" java.lang.ClassNotFoundException: org/jruby/Main
  at java.lang.Class.forName0(Native Method)
  at java.lang.Class.forName(Class.java:186)
  at org.flatland.drip.Main.mainMethod(Main.java:38)
  at org.flatland.drip.Main.main(Main.java:19)

The second time it just hangs after printing the stack trace. It also leaves a java process running after I ctrl-C it. I've killed all drip and java processes and tried again a few times, with the same results.

I assume this isn't JRuby-specific, but that's what I tried with.

ninjudd commented

Is this running from a checkout or standalone?

I just released a new version of the jar that may fix this issue running standalone.

ninjudd commented

@amalloy we should use the develop branch from now on. I think this issue may have been caused by the bin script using the bootclasspath but running against an old jar that didn't use the system classloader.

iconara commented

Was running standalone, but now I've updated and it at least running ruby -v works fine.

ninjudd commented

Great. Let me know if you have any other problems.