Separate Qpid Broker for Java and 0-x JMS Client in source tree

As discussed here:

http://qpid.2158936.n2.nabble.com/DISCUSS-Drop-the-AMQP-0-x-client-from-the-Qpid-for-Java-7-0-release-td7657770.html

The proposal is to move the code and documentation that comprises the 0-x client to its own SVN root:

https://svn.apache.org/repos/asf/qpid/qpid-jms-0-x

The Java Broker and integration tests suites will remain at: https://svn.apache.org/repos/asf/qpid/qpid-java

Maven dependencies will be used to pull in the appropriate 0-x client for integration testing purposes (as we already do with the Qpid JMS Client).

The qpid-common module (and maven release artefact) will be eliminated.

• Classes that the Broker requires will be moved into the class hierarchy of the existing plugin modules amqp-0-10-protocol and amqp-0-8-protocol e.g. org/apache/qpid/server/protocol/vx_y.* There is some generic code used by many modules such as BindingURL whose copy shall live in broker-core.
• Code that the 0-x client requires will be copied into the client module. The package names will be unchanged.

This will allow the Broker and 0-x Client to co-exist in the same JVM without class loading collision. Class movements will be organised in such a way to preserve SVN history.

The structure of trunk qpid-jms-0-x will look like:

• qpid-jms-0-x
  + client
  + example
  + jaa
  + example
  + ra
  + docs
  + jms-client-0-10
  + jms-client-0-8

There will need to be a new parent POM.