On Mon, Sep 1, 2008 at 12:30 PM, Victor Hugo Borja <[EMAIL PROTECTED]> wrote: > I've fixed the Java.load issue for JRuby 1.1.4 in > http://tinyurl.com/5rbfme, however I don't like much the fact that > jars need to be loaded on the > system class-loader. > For the javadoc tool adding tools.jar seems like the only way to make it > find the standard doclet. > And for some reason, java_test_frameworks_spec.rb was failing unless all > jars were loaded on system CL. > > So we still load the buildr classpath in the system CL. :)
Javadoc has always had this flaw, and there's no elegant solution for it. On the other hand, we can always run Javadoc from the command line, so we don't need to twist the CL around just to please it. I'm still hopeful we can find a more elegant solution for the test frameworks. > Side note: should we upgrade buildr to require jruby 1.1.4, it seems like it > loads/runs faster than 1.1.3 ? Only if we can't find a way to support both. We have to start assuming longer upgrade cycles. I started testing against a version of JRuby I installed using MacPorts, and it's reporting 1.1.3 rev 6586 (the JRuby site has 1.1.3 rev 7243) Assaf > > On Sun, Aug 31, 2008 at 12:51 PM, Assaf Arkin <[EMAIL PROTECTED]> wrote: > >> It's a problem somewhere in lib/java/jruby.rb, the load method fails >> when trying to mess with the classloader. >> >> Assaf >> >> On Sun, Aug 31, 2008 at 10:32 AM, Victor Hugo Borja <[EMAIL PROTECTED]> >> wrote: >> > It seems trying to run an spec using jruby 1.1.4(java 6) fails when >> loading >> > sandbox.rb, also tried 'load' instead of require with same results... >> > >> > [EMAIL PROTECTED]:~/hk/buildr$ /opt/jruby-1.1.4/bin/jruby -S >> > /opt/jruby-1.1.4/bin/spec spec/application_spec.rb >> > /opt/jruby-1.1.4/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:34:in >> > `require': IO error -- /home/vic/hk/buildr/spec/sandbox (LoadError) >> > from /home/vic/hk/buildr/./spec/application_spec.rb:17 >> > from /home/vic/hk/buildr/./spec/application_spec.rb:14:in `load' >> > from >> > >> /opt/jruby-1.1.4/lib/ruby/gems/1.8/gems/rspec-1.1.4/lib/spec/runner/example_group_runner.rb:14:in >> > `load_files' >> > from >> > >> /opt/jruby-1.1.4/lib/ruby/gems/1.8/gems/rspec-1.1.4/lib/spec/runner/example_group_runner.rb:13:in >> > `each' >> > from >> > >> /opt/jruby-1.1.4/lib/ruby/gems/1.8/gems/rspec-1.1.4/lib/spec/runner/example_group_runner.rb:13:in >> > `load_files' >> > from >> > >> /opt/jruby-1.1.4/lib/ruby/gems/1.8/gems/rspec-1.1.4/lib/spec/runner/options.rb:98:in >> > `run_examples' >> > from >> > >> /opt/jruby-1.1.4/lib/ruby/gems/1.8/gems/rspec-1.1.4/lib/spec/runner/command_line.rb:19:in >> > `run' >> > from >> /opt/jruby-1.1.4/lib/ruby/gems/1.8/gems/rspec-1.1.4/bin/spec:4 >> > from >> > /opt/jruby-1.1.4/lib/ruby/gems/1.8/gems/rspec-1.1.4/bin/spec:19:in `load' >> > from /opt/jruby-1.1.4/bin/spec:19 >> > >> > JRuby 1.1.3 doesn't have this issue. >> > Anyone else having this problem, or any idea on how to get it to work? >> > >> > -- >> > vic >> > >> > Quaerendo invenietis. >> > >> > > > > -- > vic > > Quaerendo invenietis. >
