> I hate our source layout with a passion. The top level trunk
> containing just
> qpid/ is remarkably irritating and makes merging between the branches
> a
> PITA. I'd rather see a split along functional terms. The build system
> would
> need to be complicated slightly to allow this, but a couple of simple
> Makefiles should be sufficent. I'd think something like:
> 
> trunk/
>    broker/
>       java/
>       cpp/
>    client/
>       java/
>       cpp/
>       ruby/
>       python/
>    tools/
>       management/
>          jmx-gui/ <-- eclipse plugin
>          jmx-cli/ <-- JMX console
>          qman/
> 

I am not sure management should be under tools. Each broker implementation 
should host its management agent and each console relies on an implementation 
of the management protocol. So I would rather see the implementation of the 
management protocol under broker/language and client/language and have the 
consoles and additional agents under /tools/management. That is to say that if 
qman is under tools/management/ then we must have it C++ counterpart hosted 
there too.

Reply via email to