[IMAP] Projects' structure

2010-08-19 Thread Eric Charles

 Hi Everybody

After splitting the tests from functional to their store projects 
(IMAP-187), we could centralize the test infrastructure present in 
different projects:

- apache-james-imap-deployment
- apache-james-imap-protocol-tester
All going to  apache-james-imap-seda

apache-james-imap-decoder shouldn't apache-james-imap-decode be fusioned 
with apache-james-imap-message which already contains the encode stuff ?


This does not bring real direct value, but we'll have less projects 
(easier for a newbie and to talk about it).


Any thoughts ?
Tks,

Eric


-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org



Re: [IMAP] Projects' structure

2010-08-19 Thread Norman Maurer
Comments inline...

2010/8/19 Eric Charles e...@apache.org:
  Hi Everybody

 After splitting the tests from functional to their store projects
 (IMAP-187), we could centralize the test infrastructure present in different
 projects:
 - apache-james-imap-deployment
 - apache-james-imap-protocol-tester
 All going to  apache-james-imap-seda

I would move all to apache-james-imap-protocol-tester.


 apache-james-imap-decoder shouldn't apache-james-imap-decode be fusioned
 with apache-james-imap-message which already contains the encode stuff ?

sounds good too..


 This does not bring real direct value, but we'll have less projects (easier
 for a newbie and to talk about it).

 Any thoughts ?
 Tks,

 Eric

Go ahead :)

Bye,
Norman

-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org