headius on master
Remove the rest of Nailgun Nai… Merge pull request #6597 from h… (compare)
headius on master
Remove BSF support This remove… Merge pull request #6596 from h… (compare)
GitParameterPluginAvailable
always set to false
. Instead, if I prepend the java class name with Java.
I get the following backtrace: http://dpaste.com/1SX9VK9Java.
prefix or without it?
include Java
would 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 Java
into will gain some peculiar side effects of our module/package logic that lives in the Java
module.
include Java
now, and use require 'java'
only as future-proofing in case we don't load it by default some day.
I think I have a definitive proof of JRuby's Thread.current
object changing in the middle of a process run... Like, local block-level variables remain the same, everything works as expected, but Thread.current
is completely different (different ruby object instance, different object_id
, different thread-local contents, etc) at the end of the method compared to the value at the beginning of the same method. This completely breaks my mental model of how computers work. Anybody else seen or experience anything like that?
P.S. In case it is relevant:
jruby.worker.script=SharedTogo::Workers.start_all!
Concurrent::AtomicBoolean
shutdown flagat_exit
block is used to set the shutdown
flag to true
Thread.list
at the end of the method contains a single value in each thread - the new thread object for each thread. Meaning in each of 4 worker threads Thread.list == [Thread.current]