Vincent Massol wrote:
>
> Here are proposals/questions for naming/locations of the deliverable files
> of Cactus :
>
>
> 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, ...
Ah. I was just thinking of the date on the 'whole package' tgz/zip, not
each part.
cactus-20010404.tgz
and since the tgz should unzip (ok, tar) into a cactus-20010404
directory, then things stay together.
> 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
That's a good question.
This nice thing about the inversion of that :
...../builds/jakarta-commons/release/cactus/v1.0/cactus-1.0.tgz
...../builds/jakarta-commons/nightly/cactus/cactus-20010404.tgz
is that from the release directory, we can add links to the latest of
each component, so you can gather all of them at once w/o running in and
out of component subtrees.
...../builds/jakarta-commons/release/cactus-1.0.tgz
...../builds/jakarta-commons/release/beanutils-1.0.tgz
...../builds/jakarta-commons/release/dbcp-1.0.tgz
same idea with nightly
geir
--
Geir Magnusson Jr. [EMAIL PROTECTED]
Developing for the web? See http://jakarta.apache.org/velocity/
