on 4/4/02 1:21 PM, "Jason van Zyl" <[EMAIL PROTECTED]> wrote:
> You mean for the central repository? For some reason I always thought
> you meant for each individual project. If this is for the entire central
> repository then I'm not averse to that idea. But the repository should
> still be the location for released versions of tools. For logging I
> think this is a good idea. I still do not agree that it is a good thing
> to check in N developmental builds.
>
> If using CVS for the central repo is what you mean.
I can't believe all this time you didn't understand what I was saying. Sigh.
:-(
I do in fact mean to use CVS for the central repo.
>> That way, I can reference an unreleased beanutils and you can reference
>> released versions.
>
> All you had to do was name it something different to identify it as
> different and all would have been well.
But that doesn't mean anything when you have:
commons-foo-1.0-dev.jar
I would then have to put the date into the file name...it is much easier to
stick the .jar files into CVS and just reference a TAG.
Please create a jakarta-turbine-jars repo.
Then, what we will do is check all the files in
/www/jakarta.apache.org/turbine/jars into that repo. In the /www/*/jars
directory, we will then put a .htaccess file with lines like this:
RedirectMatch turbine-3.0-dev.jar
http://cvs.apache.org/viewcvs.cgi/~checkout~/jakarta-turbine-jars/turbine-3.
0-dev.jar
I just talked to Greg Stein (author of viewcvs and works at collabnet) and
asked him to add a feature to viewcvs to set the Last-Modified: header when
doing a checkout like the example above as well as upgrade viewcvs on
apache.org. That way, we can use that to see if the file on disk needs to be
updated or not.
Also, Greg pointed out that in the future, when everyone is using subversion
(replacement for CVS), this operation will be a simple HTTP process because
Subversion implements WebDAV.
-jon
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
