Craig,
> If we make the two choices (which version and which local name)
> independent request parameters, we've covered all the
> combinations and permuations.
The idea I had was for the request URI to be project based. The response to
that stable URI would be descriptor content. Part of the d
Nick,
> Two problems here
> * The uri to find a needed jar.
> * How to store the jar on the local filesystem
Does the URI (request) and descriptor (response) solution I proposed not
address those goals? That approach decoupled the naming systems.
--- Noel
-
On Sat, 1 Mar 2003, Nick Chalko wrote:
> I think we should handle these cases
>
> * uri to find
> o Specific version
> o latest released. (blank )
> o latest nightly
> * Jar name on local filesystem
> o with complete version
> o without
Craig R. McClanahan wrote:
On Sat, 1 Mar 2003, Stefano Mazzocchi wrote:
[EMAIL PROTECTED] wrote:
Having a file encode --.type has been very
useful for us.
Yes, it's often different from what the project creates and distributes,
but I (and others) have been bitten by
commons-logging.jar, str
