|
This is resolved with 0.9.5, but... If jruby-rack didn't bundle its own version of Rack this wouldn't be an issue and people could choose whatever version of Rack was suitable for their environment. Agree, actually as jruby-rack user I didn't mind to have that dependency, I mean, warble already vendorize rack gem and it could be a requirement for jruby-rack custom usages. Gary Weaver suggested the following work around: – cut here –
then put the jruby-rack and jruby-complete jars you want to use in the lib/ dir. The jruby-rack snapshot containing this fix is: You'll need to find the jruby jar you want to use and put it in the lib dir or remove that part from above. My related blog entries: If you could post this into the Kenai ticket if it works for you, that would be great. (just got my Kenai acct. stuff straightened out) A few more notes about the workaround:
Gary As of 7a14ac4, JRuby-Rack allows a newer rack to be loaded and doesn't force its vendored copy on you. |
||||||||||||||||||||||||||||||||||||||||
Well after dive into jruby-rack code and jar file finally I found the problem.
jruby-rack-0.9.4.jar doesn't contain rack/lock.rb!!! that's it.
Rack::Lock is just used with some database adapters that's the reason why it just crashes sometimes.