Le 25/03/2011 16:32, Rajith Attapattu a écrit :
Proposed structure.
=================
1. I would like to see the following sub projects under Qpid with their own
top level svn directory.
qpid/transport/{trunk/branch}
qpid/client/{trunk/branch}
qpid/broker/{trunk/branch}
qpid/qmf/{trunk/branch}
2. Each sub project should ideally have the following directories .
/doc , /common, /test
For example for "qpid/client" we may have,
/doc, /common, /test, /java, /cpp, /python, /ruby ........
Shouldn't a project be more language specific? For example I don't think
the C++ and Java brokers/clients should necessarily be tied by the same
release schedule. Thus I'd rather suggest a more granular structure like:
qpid/client-java
qpid/client-python
qpid/broker-cpp
qpid/broker-java
etc...
Would that make sense ?
4. I am sure everybody will now have questions about the build system :) -
I believe it's best to discuss that important topic in it's own thread or
atleast in a separate email from this one:).
I will wait for some response on the structure before I get into
discussing the build system.
*cough* Maven anyone ? ;)
Emmanuel Bourg
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
