On 25 March 2011 17:13, Emmanuel Bourg <ebo...@apache.org> wrote:
> 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 ?
>
>
I very specifically want to avoid having language specific silos. Clearly a
lot of things are going to be language specific, so a structure of
client/trunk/java
client/trunk/python
...
broker/trunk/cpp
broker/trunk/java
Is going to make sense...
However you should also have
broker/trunk/systests
Since the system test for a broker should be mostly the same (if the brokers
look alike - which they should be made to do).
On the client side what we're really looking at is, for many (most)
languages, wrapping a lower level client... thus they would be mostly the
same under the skin, dependent on a common core (and thus having a single
release schedule most likely).
-- Rob
>
>
> 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
>
>
