More out of date certs! Too many locations, dude.
Fixes #1312. File.expand_path(%q{NUL}) broken
Revert "Classpath urls should still use expand_path to properly canonicalize the path.  This fixes no reported issue"

This reverts commit 429149e7f5b9114ff8f6326bd72fde5a1f0a941b.
Add Comparable to Symbol.
Add Socket::SOMAXCONN to fix #1385.
Bump for 1.7.10
Don't use global runtime to try and resolve jar files which are part of runtimes init
Make json shared so 1.8 can see it since rg default gem already lists it as installed
Whitelist branches to build on Travis
fix +x bits in the bin files
fix shebang not to use local install
use local jruby install for tesla plugin
use older ruby DSL for pom.rb
Implement more Addrinfo-related logic throughout socket ext.

* Addrinfo.getaddrinfo
* Socket and ServerSocket binds that take Addrinfo
* Correct logic for SO and SOL constants in BasicSocket
* ServerSocket for listens in socket.rb

Conflicts:
	core/src/main/java/org/jruby/ext/socket/RubySocket.java
Implement BasicSocket.for_fd and related fixes.

* for_fd consumes the given fileno/descriptor and initializes the
  type of socket for_fd is called against (TCPServer, etc).
* RubyTCPServer no longer keeps a separate reference to the server
  channel nor the address, to allow for_fd initialization.
* ChannelDescriptor will now also not decrement the reference
  count during finish logic unless close is specified. With the
  old logic, non-closing finish would still produce an error on
  future non-closing finish when it should do nothing at all.

Conflicts:
	core/src/main/java/org/jruby/ext/socket/RubyBasicSocket.java
Return 0 to Socket.getaddrinfo when 2nd arg is nil
Update to jsr292-mock 1.1.
Reenable respond_to? caching logic.

The respond_to? call site logic was disabled because it did not
take into account respond_to_missing?. Whenever respond_to?
returns false, 1.9+ needs to check respond_to_missing? in case the
method in question is implemented by method_missing. We disabled
all respond_to? caching until we could figure out a safe way to do
this caching in 1.9 mode.

In this commit, we use the following logic to know whether we can
cache the result of a respond_to? call:

IF we are in 1.8 mode
OR respond_to? returned true
OR respond_to_missing? is not overridden
THEN cache

We will not cache, then, if we're running in 1.9 mode AND
respond_to? returned false AND there's a custom
respond_to_missing? defined. This should cover all appropriate
failure cases and allow us to cache the much more common normal
respond_to? cases.

Numbers before and after:

BEFORE:
                                          user     system      total        real
control, 1 and :to_ary                0.030000   0.000000   0.030000 (  0.031000)
1m 1.respond_to?(:to_ary)             0.060000   0.000000   0.060000 (  0.061000)
1m 1.respond_to?(:to_ary,true)        0.070000   0.000000   0.070000 (  0.069000)
1m 1.respond_to?(:next)               0.040000   0.000000   0.040000 (  0.034000)
1m redefined obj.respond_to?          0.020000   0.000000   0.020000 (  0.025000)
1m varying name respond_to?           0.030000   0.000000   0.030000 (  0.026000)

AFTER:
                                          user     system      total        real
control, 1 and :to_ary                0.030000   0.000000   0.030000 (  0.032000)
1m 1.respond_to?(:to_ary)             0.010000   0.000000   0.010000 (  0.011000)
1m 1.respond_to?(:to_ary,true)        0.010000   0.000000   0.010000 (  0.015000)
1m 1.respond_to?(:next)               0.010000   0.000000   0.010000 (  0.011000)
1m redefined obj.respond_to?          0.020000   0.000000   0.020000 (  0.023000)
1m varying name respond_to?           0.020000   0.000000   0.020000 (  0.024000)

In additionm this should reduce calls to our per-class cache
substantially in cases where the argument passed to respond_to? is
the same and the target object's type is not changing.
Temporary fix for cost of Hash#[] dynamically calling #default.

This fix adds "default" to the list of methods we build up a
per-runtime set of call sites for. I consider this a temporary
fix because that set of sites is a matrix of class count * method
count, so adding default adds another entire row/column when it
will only be used from one class.

It's clear we need some better logic for doing call site caching
for dynamic calls in Java code, but this will work for the moment.
Reduced the number of String allocations for the NONE parameterList case.