Upgrade to JRuby 1.7.8 (TORQUE-1180)
Ensure any message size can be persisted (TORQUE-1161)

We need to make sure that HornetQ's min-large-message-size is smaller
than its journal-min-size so that every message can either be stored
in the journal or in the large message store.
Implement the rack.errors interface for TorqueBox::Logger (TORQUE-1177)
Let users override where TorqueBox::FallbackLogger writes to (TORQUE-1178)

Set ENV['TORQUEBOX_FALLBACK_LOGFILE'] to overwrite where the logs get
written. This is mostly useful in testing scenarios, like in the
logger_spec.rb example in this commit.
Remove JRuby 1.7.4 / Rails 4 workaround since we're on JRuby 1.7.8
Add a formatter to TorqueBox::Logger (TORQUE-1163)

TaggedLogging in Rails 4 requires the logger to support
getting/setting a formatter.
Leave min-large-message-size at the AS7 default (TORQUE-1161)
Fallback to a hash-backed session store to ease testing (TORQUE-1016)

Instead of adding this to torquebox-no-op, it felt cleaner to just
have our session store implementation detect if TorqueBox is
available. If not, the session gets backed by a regular hash.
Actually use SessionData instead of Hash (TORQUE-1016)

This ensures in testing scenarios our real session store and this
fallback one behave the same.
Next version is 3.0.1
Revert "Revert rubygems retry hacks to test against rubygems.org changes"

This reverts commit 8e2839f2dcfc7b5a0013bb50685e42b4719150f9.

This is a stopgap until we host our own rubygems.org mirror.
Fix DeployUtils.run_command on Windows (TORQUE-1172)
Upgrade yard and exclude a couple of files to try and get CI building rdocs again
Better handle rubygems.org failures during build assembly
Publish incrementals under 1.8 instead of 1.9 to fix yardoc generation
Try again to make yardoc produce meaningful docs on CI
Fix reset_session in Rails 4 (TORQUE-1183)

Prior to Rails 4, Rails took care of clearing the contents of the
session hash on our behalf after session.destroy was called. In Rails
4, this was changed to only call session.destroy so we'll clear the
contents ourselves and invalidate the Java session.

Without this change, under Rails 4 the user would get a new Java
session but it contain the exact same session data as their previous
session, effectively making reset_session do nothing.
Perhaps I'll get CI producing correct yardocs one of these days
remove stray puts
Revert "Next version is 3.0.1"

This reverts commit 990d09aef787ab6c60dfa202c064fcdcb6856bda.

Master will stay on 3.1.0 for now, but move to 4.0.0 soonish.