On 1/17/02 2:12 AM, "Jon Scott Stevens" <[EMAIL PROTECTED]> wrote:

> on 1/16/02 12:30 PM, "Sam Ruby" <[EMAIL PROTECTED]> wrote:
> 
>> Life is easy when you work primarily on one project.  When you work on
>> muliple projects, the problem gets way more complicated.  What happens when
>> every project checks in their own xml parser, or -dev version of torque?
>> Which one do you use?
>> 
>> - Sam Ruby
> 
> You guys aren't getting it. All I'm saying is that instead of storing the
> files on disk in a directory, that you store them in a CVS repo (on disk).
> 
> Instead of:
> 
>   http://jakarta.apache.org/gump/jars/foo.jar
> 
> You would have a url something like this:
> 
>   http://cvs.apache.org/viewcvs.cgi?get=foo-1.1.jar&version=1.0
>   http://cvs.apache.org/viewcvs.cgi?get=foo-1.1.jar&version=1.1
> 
> Here is a better example: Torque isn't released yet. So, all the versions
> say: torque-3.0-dev.jar. How do you know which version of 3-0-dev.jar is the
> right version? What if you need yesterdays version instead of today's?

Either the daily snapshot has a date on it like what is being produced so
people can distinguish and or call it torque.jar and place the information
in the manifest. And right now the auto jar uploader works with timestamps
so if we change torque, and upload a new jar to the repository then it will
come down the next time people try to update.

 
> -jon
> 
> 
> --
> To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

-- 

jvz.

Jason van Zyl

http://tambora.zenplex.org
http://jakarta.apache.org/turbine
http://jakarta.apache.org/velocity
http://jakarta.apache.org/alexandria
http://jakarta.apache.org/commons



--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to