allow PATCH verb to be processed by the ruby application

Sponsored by: Lookout, Inc.

Conflicts:
	src/main/java/org/jruby/rack/UnmappedRackFilter.java
	src/spec/ruby/rack/filter_spec.rb
better client EOF (socket abort "Broken pipe") detection in JRuby::Rack::Response
... we're now "officially" handling Jetty and maybe a bunch of others due EofException
travis-ci `sudo: false` is is
`gem update --system 2.2.3` on travis-ci
setup oss.sonatype.org deployment

needed to do the "install gems" differently since it conflicted with
the main artifact.

if snapshot version ```$mvn deploy``` will deploy the artifact to
https://oss.sonatype.org/content/repositories/snapshots/ and the released
version will go to a staging repository on https://oss.sonatype.org/content/repositories/

it is also possible to use the maven release mantra:
* mvn release:prepare
* mvn release:perform
setup rubygems repository & let us roll jruby-openssl 0.9.6
activate -P jars by default due running with `mvn package` only ...
[travis-ci] exclude all of jruby-head with openjdk6
only run t is1_9 he compat-version spec on JRuby < 9k
[travis-ci] there seems to be a constant failure on TRAVIS=true with the application pool
[travis-ci] jruby-head should be fine ... from now on :over-9000:
better servlet (3.0) specific API testability
support configuration of `Response.swallow_client_abort?` (with e075f34f fixes #186)
just keep the jruby-home when set by jruby to "uri:classsloader:/META-INF/jruby.home"
use distributionManagement instead of (sonatype) pom parent
Merge branch '1.1-stable'

* 1.1-stable:

  use distributionManagement instead of (sonatype) pom parent
  just keep the jruby-home when set by jruby to "uri:classsloader:/META-INF/jruby.home"
  support configuration of `Response.swallow_client_abort?` (with e075f34f fixes #186)
  better servlet (3.0) specific API testability
  [travis-ci] jruby-head should be fine ... from now on :over-9000:
  [travis-ci] there seems to be a constant failure on TRAVIS=true with the application pool
  only run t is1_9 he compat-version spec on JRuby < 9k
  [travis-ci] exclude all of jruby-head with openjdk6
  activate -P jars by default due running with `mvn package` only ...
  setup rubygems repository & let us roll jruby-openssl 0.9.6
  setup oss.sonatype.org deployment
  `gem update --system 2.2.3` on travis-ci
  travis-ci `sudo: false` is is
  better client EOF (socket abort "Broken pipe") detection in JRuby::Rack::Response ... we're now "officially" handling Jetty and maybe a bunch of others due EofException
  allow PATCH verb to be processed by the ruby application
update pom to generate sources/javadoc and sign
re-arrange release steps