As you may be aware, open4 doesn't work on jruby, because it uses fork which isn't JVM friendly.
I am able to get jruby 1.6.x working by adding an alternative implementation of RemoteTask.run which uses jruby's popen3. This is done by way of selective mixin of new Open3 or Open4 modules. Details of how this works in jruby is commented in open3.rb.
Move RemoteTask.run into open4 mixin and add open3 mixin for jruby
Add require 'thread' for Mutex
Comments on Open3
More comments arround Open3/4
Hi, could I get any feedback on this? Concerns? Prefer it done a different way? Thanks.
I am facing the same issue with jruby 188.8.131.52.
I saw another solution from almost 3 years ago from jdamick using the Java ProcessBuilder (https://github.com/jdamick/vlad).
Any feedbacks would be great :)
If it helps you @mazhout or anyone reading this, if you are using Bundler with your deployment Rakefile, you can reference a working patched rake-remote_task via the following in your Gemfile:
:git => 'git://github.com/dekellum/rake-remote_task.git',
:tag => 'v2.0.6-jruby.1'
I'll keep these tags around, or fork your own.
Thanks for the patch ;)
"I'm tired of non-communication. I've released this..." see above.
Sorry. I'm not too interested in doing multi-platform support on this. Releasing using mri seems like a fair compromise. I'm going to close this.