Pin rake to a version that supports Ruby 1.8
RackChannel was swallowing newlines (TORQUE-1212)

Our RackChannel used for env['rack.input'] was swallowing newlines on
calls to `gets`. This broke Rack 1.4.1's multipart parsing, although
Rack 1.5.2 was unaffected.
Wait a bit longer in transaction_spec in case we hit a full GC
Tired of that dm-messaging-test.db hanging around after integs
Fix servlet_store and Rails 4 NullSessionHash (TORQUE-1196)

This is our second try at fixing this, and this time we actually use
NullSessionHash to verify the fix.
Update to latest polyglot release to stay in sync with Immutant.
Looks like we still need to clear the java_session (TORQUE-1196)
Make sure we generate .bat files for all binaries (TORQUE-1223)

This also fixes #181 on GitHub issues.
Remove our NonLeakingLoadService hacks (TORQUE-1222)

The leaks these hacks fixed have been fixed upstream in JRuby for
quite a while now, so it's safe to pull these hacks out.
Bump JRuby to 1.7.12 (TORQUE-1224)
Add a small sleep to ease thread scheduling for zero_downtime_deploy_spec

This just ensures the thread doing the runtime restarts has a higher
chance of running more often on machines with low CPU counts, like CI.
Use IPv4 for integration test client to fix sporadic DNS issues on CI
Don't cache TB services in the registry (TORQUE-1217)

When looking up a TorqueBox service via TorqueBox.fetch, don't cache
the result in the TorqueBox::Registry since that prevents the service
runtime from being garbage collected and doesn't fetch the updated
service after a zero downtime deployment of the services runtime.
Pin execjs version to one that still works in 1.8 mode
Make sure Rack responses are considered commited by jbossweb (TORQUE-1215)

Otherwise any responses with an empty response body and an error (4xx,
5xx) response code will end up with some default content supplied by
JBossWeb.
Pass the "--profile.api" command-line flag to JRuby in a way that actually works
Don't read until EOF when asked to read > 4096 bytes (TORQUE-1228)

This fixes an issue where when asked to read a request body amount
greater than 4096 bytes we were actually reading the entire request
body into memory, leading to OutOfMemory situations on large file
uploads.
Ensure ActiveSupport::Cache::TorqueBoxStore requires 'torquebox-cache' (TORQUE-1226)
Upgrade to jruby-maven-plugins 1.0.2
newer jruby-maven-plugins needs a spec/ directory