Start moving away from dependence on JavaArray objects.

All Java arrays that are proxied into Ruby get wrapped with an
ArrayJavaProxy instance. However, the paths to create that wrapper
usually involve constructing an intermedate JavaArray wrapper as
well, slowing down allocation. This change makes the following
changes to Java array proxies:

* ArrayJavaProxy and subclasses are no longer allocatable.

* All paths that created array proxies indirectly now create
ArrayJavaProxy instances directly, avoiding the intermediate
JavArray object

* The JavaArray wrapper is created lazily only when needed.

Additional fixes are coming that will do more to avoid standing up
the JavaArray object.
Eliminate creation of JavaArray through normal operations.
Improve construction of Java arrays and add type.new_array.
Move new array-related utility methods to a common location.
Remove some methods; forgot to save.
Up javac version to 1.6.
Fix compilation error caused by my unsaved buffer.
Add ArrayUtils class that was supposed to have been added already.
Set JIT threads to minimum priority, so they don't dominate CPU.
Merge pull request #427 from dvorak/master

Don't override default_exec_format method for rubygems

Thank you.
Add methods from Java* internal classes to java.lang equivs.
jruby-7029: fix add_parameter_annotation, it was untested and broken.
Properly set up the toplevel scope under new logic. Fixes #440.

The toplevel scope for a precompiled script was getting set up
with the toplevel scope for the runtime as parent, rather than
no parent. This caused constant lookup to search Object too soon,
at the top of the lexical search. This in turn led to constants
in the hierarchy with names the same as constants in Object to be
inaccessible.
Delay init of some classes by using fully qualified names.
Remove unused import
Fix JRUBY-7032: Time#strftime %3N doesn't limit sub-seconds to 3 digits
Spec for JRUBY-7032
Fix connect_nonblock never finishing the connection.

When doing a nonblocking connection, the first SocketChannel
connect call initiates the connection process. If connect is
called again, it will always raise ConnectionPending, which we
propagated as EINPROGRESS. As a result, simply calling
connect_nonblock repeatedly never finished the connection process
by calling finishConnect. Our select loop, however, did have a
finishConnect in it, so doing connect_nonblock + select worked
ok. This change moves the finishConnect into RubySocket's connect
logic and calls that once the connection has been initiated.
Remove finishConnect hack for JRUBY-5165.

Commit d3c0496 moves the finishConnect into the Socket connect
logic where it belongs.
Merge pull request #441 from xaviershay/jruby-7029

jruby-7029: fix add_parameter_annotation, it was untested and broken.

Thanks.