Warbler configuration and jruby version

I just installed jruby-1.4.0 to play with it. However, I notice that warbler packs this by default when deploying rails. My production uses jruby-complete-1.3.1 (which I added to my lib directory to freeze the version), but warbler adds jruby-core-1.4 when it packs everything. This bothers me a bit since I don't need any version problems or conflicts, I just want to freeze my jruby version so that I have to explicitly change it when I am ready to upgrade. Does anyone know a better way to achieve this?

The documents that I read say that out of all WARPAR_HOME all banks will be accepted, so I assumed that there is jruby-core-1.4, but this is not so. How can I omit this from deployment or, in particular, say: "give me only the XX version of jruby"

I found the string home by running:

jruby -S gem which warbler 

What gives

 /opt/local/share/java/jruby/lib/ruby/gems/1.8/gems/warbler-0.9.14/lib/ 

But there is only a rack in it, there is no link to jruby-core-1.4

Any thoughts?

+7
ruby-on-rails jruby warbler
source share
1 answer

JRuby is enabled through a separate jruby-jars stone. Install version 1.3.1:

 jruby -S gem install -v 1.3.1 jruby-jars 

And then uninstall version 1.4.0:

 jruby -S gem uninstall -v 1.4.0 jruby-jars 

If gem asks for confirmation due to dependencies, continue and answer with "y".

+9
source share

All Articles