Keith, I agree it seems the good time to start changing project layout and introduce independent sub-projects. The proposed layout looks reasonable. Although, qpid-java sub-projects will be split later into more sub-projects. Apart from the ones you listed on wiki (java-broker and java-legacy-client), it seems there will be at least one java-amqp-commons (conatining 0.8/0.9.x/0.10 AMQP classes) which can be split into protocol based sub-modules (java-amqp-commons-0_10 and java-amqp-commons-0_8-0_9_x).
Regarding 'Programming in Apache Qpid' docbook it can either be a separate top-level sub-project (as it covers cpp and java legacy client) or we can temporary move it into qpid-cpp (as the majority of content in the book is related to cpp clients or cpp bindings based clients) Kind Regards, Alex On 16 March 2015 at 18:12, Keith W <[email protected]> wrote: > Hello all, > > I believe we reached agreement on the following thread [1] that we would > reorganise trunk (to support independent component releases) once the 0.32 > was branched. > > Justin previously published a source tree layout proposal. I have just > extended it to include the Java subtree too. > > > https://cwiki.apache.org/confluence/display/qpid/Source+tree+layout+proposal > > As 0.32 is branched (and at the voting stage), is there anything that > blocks us from beginning the re-org task? Are there comments on the > proposed layouts? > > I am ready to work with other committers to help make sure the transition > is a smooth one. > > cheers, Keith. > > > [1] > > https://www.mail-archive.com/[email protected]&q=subject:%22Re%3A+Any+ETA+on+a+QPid+0.32+release%22&o=newest >
