enebo on jruby-9.3
Including modules after a prepe… Only pass in method location fo… Merge pull request #6954 from e… (compare)
enebo on 184.108.40.206
mvncomplains about the
./mvnwis fine, and
./mvnw -Pbootstrapruns fine, but
./mvnstill complains after. (This is on JDK 1.8 on macOS 10.14) Is this expected? I ran
jruby -S rake spec:ruby:fastwhich reported 3 failures and 2 errors (Signal.list redefines CLD with CHLD if defined FAILED, plus some networking stuff that seems like it might be a platform thing). I can see that's not happening in the last Travis build. Is that expected/a problem?
GitParameterPluginAvailablealways set to
false. Instead, if I prepend the java class name with
Java.I get the following backtrace: http://dpaste.com/1SX9VK9
Java.prefix or without it?
include Javawould trigger
require 'java'if it had not already been loaded, but in all recent JRuby versions it's already there. The difference comes in where you actually
include; whatever module you
include Javainto will gain some peculiar side effects of our module/package logic that lives in the
include Javanow, and use
require 'java'only as future-proofing in case we don't load it by default some day.