jakarta-tomcat... getting messy?

["Kevin A. Burton" <bu...@relativity.yi.org>]

So just a suggestion.  why not rework things slightly in jakarta-tomcat
so that it is organized a little better?

......

-rw-r--r--   1 root     root         1.0k Mar 24 10:43 BUGS
drwxr-xr-x   2 root     root         1.0k Apr  7 09:57 CVS/
-rw-r--r--   1 root     root         2.8k Oct  8  1999 LICENSE
-rw-r--r--   1 root     root         2.6k Apr  6 14:18 README
-rw-r--r--   1 root     root         2.1k Jan  6 12:01 RELEASE-INFO
-rw-r--r--   1 root     root         2.2k Mar  2 12:42 RELEASE-PLAN
-rw-r--r--   1 root     root         1.9k Apr  6 16:13 RELEASE-PLAN-3.2
-rw-r--r--   1 root     root          14k Apr  6 17:12 STATUS.html
-rw-r--r--   1 root     root         1.7k Mar 23 17:09 TODO
drwxr-xr-x   6 root     root         1.0k Apr  7 09:57 bin/
-rwxr-xr-x   1 root     root          617 Jan 15 09:35 build.bat
-rwxr-xr-x   1 root     root          512 Mar 20 15:47 build.sh
-rw-r--r--   1 root     root         7.5k Apr  4 20:16 build.xml
-rw-r--r--   1 root     root         7.0k Mar  4 04:38 build1.xml
drwxr-xr-x   3 root     root         1.0k Apr  7 09:57 etc/
-rwxr-xr-x   1 root     root          268 Oct  8  1999 generatedocs.bat
-rw-r--r--   1 root     root          833 Jan 13 17:42 generatedocs.sh
drwxr-xr-x   5 root     root         1.0k Apr  7 09:57 proposals/
drwxr-xr-x  14 root     root         1.0k Apr  7 09:58 src/

......

Why not just have a :

./docs
./build

directory and put necessary files under those two directories? (BUGS,
LICENSE, README, etc in docs and build.bat, build.xml in build)

It also makes build.xml cleaner as you only have to put ./docs within
<jar> directives.

Also instead of ./proposals why don't we create a new CVSROOT for
proposals?  Like maybe jakarta-tomcat-proposals?

...

Kevin
-- 
Kevin A Burton (burton@apache.org)
http://relativity.yi.org
Message to SUN:  "Please Open Source Java!"
"For evil to win is for good men to do nothing."