I don't know the answer to your question but I can say why it is a warning...ArgumentProcessor is seeing this and you are already running the JVM so it is trying to point out we cannot enable ea at that point. I wonder if in the past we had not passed JRUBY_OPTS env into the JVM (but appropriately setting up the Java command-line) and somenoe realized not doing that would break sub-invokes of JRuby or something like that?
Yeah. So if we cannot tell if assertionas are enabled progrmatically we should probably disable the warning altogether. I think at one time this warning worked as expected but it appears like it must not any more.
Either I don't understand how
JRUBY_OPTSis supposed to work, or it gives misleading warnings:
We haven't launched a sub-JRuby there, and I think the argument isn't ignored:
The text was updated successfully, but these errors were encountered: