Page History

...

In the future, it may be attractive to move the messaging API into its own module.

qpid-java (proposed)

• Java broker / common / client (0-8..0-10)
• Current source location at https://svn.apache.org/repos/asf/qpid/trunk/qpid/java 
• Proposed source location at http://svn.apache.org/repos/asf/qpid/java
• The intention would be to rehome the Java tools and Java docbooks (those relating to Java Broker and Java Client 0-8..0-10) to beneath the new root.  (Note sure what will happen to 'Programming in Apache Qpid', as its content is shared)

It is anticipated that eventually, the java broker will be split from (what will become) the legacy Java client (0-8..0-10).  These will become two separate nodes at the top of the tree.

Refactored modules

• qpid-tests - Becomes part of qpid-python
• qpid-tools - Becomes part of qpid-cpp (Python tools) and qpid-java (Java tools) 
• qpid-qmf - (This is just console.py) becomes part of qpid-cpp
• qpid-specs - Already pulled into qpid-cpp, -java, -python where needed

...

• qpid-interop - A new top-level component that uses the qpid-proton and qpid-jms APIs to test interoperability and conformance of AMQP 1.0 clients and intermediaries; this would be the latter-day version of qpid-tests, focused on AMQP 1.0
• qpid-messaging-api - This would be broken out from the qpid-cpp tree; it might make sense to make it a 1.0-only variant of the messaging API
• qpid-management - An implementation of the AMQP Management specification

Not specified here

• Qpid Java-related components

Previous discussion

• Source tree layout discussion thread from 2013