[
https://issues.apache.org/jira/browse/QPID-7622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15837725#comment-15837725
]
Keith Wall commented on QPID-7622:
----------------------------------
We need to remember qpidversion.properties. Both Broker and Client both load
this file from the classpath. At very least we need to ensure that they
reference unique resources.
> Separate Qpid Broker for Java and 0-x JMS Client in source tree
> ---------------------------------------------------------------
>
> Key: QPID-7622
> URL: https://issues.apache.org/jira/browse/QPID-7622
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker, Java Client
> Reporter: Keith Wall
> Fix For: qpid-java-7.0
>
>
> 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-amqp-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}}.*
> * Code that the 0-x client requires will be moved into the class hierarchy of
> the client {{org/apache/qpid/client}}.
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
