Re: Project source structure

tom strickland wrote:
> On the other hand, with so many changes going on and what with the CVS 
> system's untidy way with deleted or moved files and especially with 
> directories, I would be tempted to start a new project with a clean CVS 
> repository.

I'm a little bit afraid that starting a new project will divise the 
actually small community interested in Sandstorm.  But, if people in 
this list want to start and especially *participate* on a new project, I 
agree to start a new one.

However, if we go this way, we have to take some decisons about project 
infrastructure.
So, I propose that the new project be named Sandstorm and hosted at 
java.net.  The package prefix could be net.java.sandstorm and all 
package names could be renamed in lowercase.  By exemple, we could have 
the package net.java.sandstorm.adisk

The repository could be structured in modules like this:

Sandstorm
   |
   +---adisk
   |       +---src
   |
   +---asocket
   |       +---src
   |
   +---atls
   |       +---src
   |
   +---gnutella
   |       +---src
   |
   +---haboob
   |       +---src
   |
   +---http
   |       +---src
   |
   +---nbio
   |       +---src
   |
   +---sandstorm
   |       +---src
   |
   +---util
           +---src

Like I already said, each 'src' directory could have a 'main', 'test' 
and optionally a 'jni' sub directory:

               src
                +---jni
                +---main
                +---test


Go for it?

Regards,
Jean M








-------------------------------------------------------
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