Project source structure

Hi,
Actually, SEDA build process is messy.  We could define a better 
directory structure.

Personally, I don't like that Haboob, Gnutella, nbio and all libs 
(aDisk, aSocket, aTLS, Gnutella, http) are in the same directory 
structure that Sandstorm because we could want to develop and release 
each of them separately.  Also presently, test and source code are 
intermingled.

In the same way that Eclipse developers do, we could separate our 
project in 10 independents modules like this:

seda
   +---Apps
   |    +---Gnutella
   |    |      +---src
   |    |
   |    +---Haboob
   |           +---src
   |
   +---Libs
   |    +---aDisk
   |    |      +---src
   |    |
   |    +---aSocket
   |    |      +---src
   |    |
   |    +---aTLS
   |    |      +---src
   |    |
   |    +---Gnutella
   |    |      +---src
   |    |
   |    +---http
   |           +---src
   |
   +---Sandstorm
   |           +---src
   |
   +---nbio
   |      +--------src
   |
   +---util
          +--------src


Each module could have its build.xml file.
Each 'src' directory could have a 'java', 'test' and optionally a 'jni' 
sub directory:

   src
    +--java
    +--jni
    +--test


Advice?

Thanks,
Jean






-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8