No common next protocol should fail handshake

Motiviation:
There is currently no means to fail the SSL handshake due to there being no common next protocol.
The current treatment of a  return value from  also results in no NextProtocolMessage being sent to the server.
According to [NPN RFC section 3](http://tools.ietf.org/html/draft-agl-tls-nextprotoneg-04#section-3) and [Google's NPN Spec, Next Protocol Negotiation Extension Section](https://technotes.googlecode.com/git/nextprotoneg.html)  if the server included a  extension.

Modifications:
-Returning  from  should result in a failed SSL handshake with alert no_application_protocol(120)
-Add unit test for this scenario

Result:
jetty npn-boot is compatible with specifications and allows a means to fail the handshake if no common next procotols found.

Bug: 446672
Signed-off-by: Scott Mitchell <scott.k.mitch1@gmail.com>
Merge pull request #5 from akamai/no_application_protocol

No common next protocol should fail handshake
Restricted build to JDK 1.7 only.
Centralized versions of dependencies and Maven plugins.
[maven-release-plugin] prepare release npn-project-1.1.8.v20141013
[maven-release-plugin] prepare for next development iteration