On 17/03/15 10:22, Gordon Sim wrote:
On 03/16/2015 06:12 PM, Keith W 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?
The tools/python stuff is to go with the c++ broker. I think the
tools/java stuff should go with the java broker/client as it has those
as dependencies. The tools/ruby stuff can probably be killed?
I'm not going to die in a ditch about this stuff, but if we are
splitting this stuff up based on components I'm not convinced it should
go with either C++ or Java brokers - as it happens I quite liked it in a
tools area and perhaps the best home for the QMF/QMF client apps stuff
is in the putative "management" tree. Sure the intention there is to
start to formulate stuff around AMQP 1.0 Management, but I think having
QMF stuff in there reminds us that we might have an exciting migration
exercise if/when we eventually decide to deprecate QMF.
From a practical perspective too although the tools/java stuff tends to
have most of its compilation dependencies on the (original) Java JMS and
the Java Broker Management Model it is *primarily* providing management
capabilities for the C++ broker, the reason that it exists in the first
place was because there wasn't a UI for the C++ broker.
As the Java Broker has an embedded UI I have visions of someone saying
"why have we got this *other* UI" .......
So basically I don't think the split is as obvious as you are
suggesting, but I'll go with the flow.
Frase
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
