@kares perhaps we will just special case anything starting with jruby.openssl. ?

how about letting unknown ones through, is that not possible?

Here's the first weird thing - why is the warning being printed twice? It turns out that JRuby runs processArguments twice!

    at org.jruby.RubyInstanceConfig.processArguments(RubyInstanceConfig.java:166)
    at org.jruby.Main.run(Main.java:224)
    at org.jruby.Main.main(Main.java:197)

    at org.jruby.RubyInstanceConfig.processArguments(RubyInstanceConfig.java:166)
    at org.jruby.Main.doProcessArguments(Main.java:468)
    at org.jruby.Main.internalRun(Main.java:257)
    at org.jruby.Main.run(Main.java:225)
    at org.jruby.Main.main(Main.java:197)

Is that the right behaviour?

As for actually fixing this issue, I can do two things - we can remove this feature that warns you about an unknown property (and that's all it is by the way - a warning - we don't 'handle' it as in removing it or something like that). But that does seem a shame as I think it's useful. Or we could add a feature that says ignore properties in jruby.openssl.* and some other known patterns. Which do we want?

aah, right - there's actually no debug lines to be printed in my script :) ... my bad thought this is more serious. at this point I do not care what the fix is - if its a useful feature for users than keep it and add jruby.openssl.* as a know pattern. maybe jruby-openssl is the only one using the jruby.xxx namespace.

@chrisseaton I think we keep going and just add jruby.openssl.* to the exclude list. We could eventually go whole hog and let libraries register these properties but that seems a bit over the top. Let's try something simple as a workaround.

@chrisseaton thanks ... and maybe we need another bug for the processArguments going on twice?

oh you already did it, just noticed