Here are proposals/questions for naming/locations of the deliverable files
of Cactus :
1) These are the current deliverables :
- Cactus runtime jar for Servlet API 2.2
- Cactus runtime jar for Servlet API 2.3
- Cactus custom Ant tasks to help automate running Cactus tests in build.xml
- Cactus source zip (the full Cactus sources, i.e. all directories under
cactus/)
- Cactus documentation for Servlet API 2.2 (it includes a snapshot of the
web site + javadoc for Servlet API 2.2)
- Cactus documentation for Servlet API 2.3 (it includes a snapshot of the
web site + javadoc for Servlet API 2.3)
- Cactus sample sources for Servlet API 2.2 (a full functional application
using Cactus w/ complete directory hierarchy and build.xml file using
automated tests)
- Cactus sample sources for Servlet API 2.3 (a full functional application
using Cactus w/ complete directory hierarchy and build.xml file using
automated tests)
- Cactus external jar dependencies zip (contains all needed jars for
building Cactus)
2) I found that even providing the external dependencies jar is too
difficult for novice users. I'd like to actually include a lib/ directory in
the delivered Cactus source zip which will contain all needed jars (thus the
external jar zip will not be needed anymore). It means that this source zip
will be addressed at novice users or users who want to quickly
build/experiment with Cactus sources. For power-users, they will download
from CVS and thus will *not* have this lib/ directory. Is that fine with you
?
3) The actual name format for all deliverable file names is "cactus-...". Do
I need to change that to be "common-cactus-..." ?
4) Here are the deliverable names I imagine to use for releases (in the same
order as point 1) above). Example taken on release 1.0 :
- cactus-22-1.0.jar
- cactus-23-1.0.jar
- cactus-ant-1.0.jar
- cactus-src-1.0.zip
- cactus-doc-22-1.0.zip
- cactus-doc-23-1.0.zip
- cactus-sample-22-1.0.zip
- cactus-sample-23-1.0.zip
- cactus-dependencies-1.0.zip (will be removed if point 2) is accepeted)
5) Snapshot names.
5a) As there are several file names for each build, I suggest a directory
per build with the date in the name : 2001-04-04
5b) At first, I did not want to put any version information in the name of
files but as some of you pointed out it is nice when you download several
snapshots. So I propose :
ex: cactus-22-20010404.jar, ...
6) Location of deliverables ?
7) Location of snapshots :
/www/jakarta.apache.org/builds/commons/nightly/cactus or
/www/jakarta.apache.org/builds/commons/cactus/nightly ? If deliverables are
put at the same location then I prefer the latter options, so we have :
/www/jakarta.apache.org/builds/commons/cactus/nightly
/www/jakarta.apache.org/builds/commons/cactus/release
Thanks for your help.
Vincent.
