I’ve run into a problem from within a rakefile when attempting to run
another jruby script with -J-D options. I was able to narrow down the
following simple case.
jruby -e “exec %(jruby -J-Djava.io.tmpdir=. --properties)”
jruby: unknown option -J-Djava.io.tmpdir=.
The same works fine under MRI. Bug?
ruby -e “exec %(jruby -J-Djava.io.tmpdir=. --properties)”
-e:1: warning: Insecure world writable dir /home/jis/compsvc/lenny/
tmp/., mode 040757
These properties can be used to alter runtime behavior for perf or
compatibility.
Specify them by passing -J-D=
COMPILER SETTINGS:
jruby.compile.mode=JIT|FORCE|OFF
Set compilation mode. JIT is default; FORCE compiles all, OFF
disables
…
-lenny
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
Forgot to mention that this happens with 1.1 and 1.1.1
On May 16, 2008, at 3:06 PM, Lenny M. wrote:
-e:1: warning: Insecure world writable dir /home/jis/compsvc/lenny/
-lenny
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
It’s because of our in-memory launcher magic. Try when running with -
Djruby.launch.inproc=false (passed to the outer JRuby).
/Nick
On May 16, 2008, at 14:08, Lenny M. [email protected] wrote:
jruby.compile.mode=JIT|FORCE|OFF
http://xircles.codehaus.org/manage_email
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
Thanks Nick. That does work. In my particular case I was just trying
to pass -J-Djava.io.tmpdir so I wound up accomplishing the same by
setting ENV[‘JAVA_OPTS’].
-lenny
On May 16, 2008, at 9:24 PM, Nick S. wrote:
-e:1: warning: Insecure world writable dir /home/jis/compsvc/
http://xircles.codehaus.org/manage_email
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email