Nick Chalko wrote:
Tim Anderson wrote:
For advocates of URI parsing, what problems are you trying
to solve?
* Discovery of "what is available"
* Repository exploring.
* Auto cleanup of repositories.
The URI spec is too loose.
I completely agree.
But I just want to add that all I wa
Why don't we just focus on:
a) getting an ASF-only repository up first, and
b) Getting the management and tooling for that
before taking on virtual hosting.
I'm failing to see the requirement for us to do that *now*.
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/peop
Here is my 20 second URI
http://host/[rootdir]/Orginzation/Product/version/
one dir each for Org, Prod, and Ver.
After that is dependent on the kind of Product. ie the java-artifact-spec.
So lets do a 20 sec java artifact spec
Stephen McConnell wrote:
Nick Chalko wrote:
Tim Anderson wrote:
For ad
[EMAIL PROTECTED] wrote:
Why don't we just focus on:
a) getting an ASF-only repository up first, and
b) Getting the management and tooling for that
before taking on virtual hosting.
I'm failing to see the requirement for us to do that *now*.
Because Apache projects using the repository would need a
Nicola Ken Barozzi <[EMAIL PROTECTED]> wrote on 25/11/2003 07:23:15 PM:
>
> [EMAIL PROTECTED] wrote:
>
> > Why don't we just focus on:
> >
> > a) getting an ASF-only repository up first, and
> > b) Getting the management and tooling for that
> >
> > before taking on virtual hosting.
> >
> > I
[EMAIL PROTECTED] wrote:
I agree it would be a nice to have, but is it a requirement for an ASF
repo?
Agree, lets wrap up the other specs first. I think we should delay,
but a week or two maybe enough.
Comment on the "/" issue. Help decidce in the version name not allowing
"release" or "
