jean-frederic clere wrote:
> 
> GOMEZ Henri wrote:
> >
> > Could we change the naming of webapp to
> > make it matching jk...
> >
> > ie :
> >
> > webapp/src/native/apache-1.3
> > webapp/src/doc
> > webapp/src/native/include
> > webapp/src/java
> > webapp/src/native/lib
> > webapp/src/native/scandoc
> > webapp/src/native/webapplib
> >
> > May be JF or Kevin :)
> 
> If we share some macro files (m4 files) for configure, life  will be more easy
> if the relative pathes are the same.
> 
> But the src does not help in jk: all is under src!
> It brings nothing to have src/native src/doc src/java... And what is src/doc?
> +++
> $ cd /home/jakarta/jakarta-tomcat-connectors/jk
> $ ls -lt
> total 12
> drwxr-xr-x   2 jakarta  betex       1024 Jun  7 09:49 CVS
> drwxr-xr-x   6 jakarta  betex         96 Jun  7 09:46 src
> -rw-r--r--   1 jakarta  betex        821 Jun  6 16:54 README.txt
> -rw-r--r--   1 jakarta  betex       2901 May 30 17:26 build.xml
> -rw-r--r--   1 jakarta  betex        437 May 30 01:05 build.properties.sample
> +++
> 
> I would propose to remove the src level in jk...
> 

i'd be ok with removing the src level in jk (and also in util).  i'm not
all that picky about directory structure.  consistency is good, though
:)

> An other thing I am thinking about: the java sources of webapp are in a flat
> structure (all in the java directory). In jk they are in ...org/apache/ajp. Does
> this make sense?
> 

i'm kind of partial to .java files living in directory structures that
match their containing packages.

Reply via email to