We had been adding . to classpath because by default the java command uses . as classpath, and we wanted to mimc that behavior for the jruby command.

[] ~/projects/jruby $ cat Blah.java
public class Blah {
  public static void main(String[] args) {
    System.out.println(System.getProperty("java.class.path"));
  }
}

[] ~/projects/jruby $ javac Blah.java

[] ~/projects/jruby $ java Blah
.

Given this, do you still feel like we should change it?

Okay, I was looking at it from the Ruby side, which doesn't include the current directory by default.

% cp /dev/null foo.rb
% irb 
irb(main):001:0> require 'foo'
LoadError: cannot load such file -- foo
        from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
        from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
        from (irb):1
        from /usr/bin/irb:12:in `<main>'
irb(main):002:0> 
% irb -I .
irb(main):001:0> require 'foo'
=> true
irb(main):002:0> 

If you are favoring Java compatibility over Ruby compatibility, then anyone affected by the problem can use the "nonexistent directory" work around to get the current directory out of -classpath.

@headius hmm, in the new load-service I put a quite some effort in to not find resources in current directory unless the "." is in $LOAD_PATH. there are a couple of test which check this but they do switch the ruby current directory to somewhere else and then the old load-service does not find it.

well I expected things to be the ruby way - like @derek-upham

maybe we should make my "omitted" testcase to test what we want to have.

Can somebody give a look on https://github.com/compiler-tech/dsl_in_action_ch4_ruby_trade . Why java -cp .:/usr/local/Cellar/jruby/9.0.0.0/libexec/lib/jruby.jar trade_dsl can't work . But jruby -I. trade_dsl.rb can work?

@jiamo classpath != load-path

the first sets "." to the classpath and the second sets it to the load-path - two different things. MRI does not to inside "." unless "." is on the load-path. the same jruby does whether it can find files on the classpath or not. jruby will honor the MRI behavior.

@mkristian thanks. In my situation I alreay compile rb files to class files, and add . to classpath, seem it does't concern the load-path?

it should be no difference whether the ruby files are compiled or not.
they are from the jruby point of view the same files, i.e. they have to be
on the load-path.

your examples should work like this:

java -cp /usr/local/Cellar/jruby/9.0.0.0/libexec/lib/jruby.jar
org.jruby.Main -I. trade_dsl

maybe even

java -cp .:/usr/local/Cellar/jruby/9.0.0.0/libexec/lib/jruby.jar
org.jruby.Main trade_dsl

did not check out your code so far.

Hi, In my situation, java -cp /usr/local/Cellar/jruby/9.0.0.0/libexec/lib/jruby.jar org.jruby.Main -I. trade_dsl.rb can work, while java -cp /usr/local/Cellar/jruby/9.0.0.0/libexec/lib/jruby.jar org.jruby.Main -I. trade_dsl still can't work, it will cause something like Error opening script file: trade_dsl (No such file or directory)

Thanks, Using java -cp /usr/local/Cellar/jruby/9.0.0.0/libexec/lib/jruby.jar org.jruby.Main -I. trade_dsl.class to get answer.