I'm trying to understand all the POV's at a higher level than URI/XML
formats.  What sorts of things
are missing from my list?   I don't care if I have a complete list -- I'm
more interested in what people want
to do as opposed to how we're going to do it.

----- Original Message -----
Sent: Saturday, March 08, 2003 4:50 PM
Subject: Re: What does the repository enable?

> Hi Ted,
> from my POV, the repository isn't only about jars and classpaths.
> --
> dIon Gillard, Multitask Consulting
> Blog:      http://www.freeroller.net/page/dion/Weblog
> Work:      http://www.multitask.com.au
> -----"Ted Leung" <[EMAIL PROTECTED]> wrote: -----
> From: "Ted Leung" <[EMAIL PROTECTED]>
> Date: 03/09/2003 10:31AM
> Subject: What does the repository enable?
> Hi guys,
> I know I'm late to the party, but...
> I know that we're discussing URI format and Andy's writing code, and I
> some code as well.  One thing
> that I haven't seen here is what functionality we want to enable by having
> a
> repository.    Here are some possible
> pieces:
> 1. Be able to download the jars that a project needs in order to get built
> 2. Be able to download the jars that a project need in order to run
> 3. Be able to generate the correct classpath so that a project can run
> 4. Allow the repository to be transparently mirrored world wide.
> 5. Allow the repository to be composed of multiple pieces, much like a
> filesystem allows mount'ing of filesystems.
> Are there any others?   In the midst of the URI format and the XML
> descriptors, I'm having trouble seeing what we are
> trying to enable.
> Ted

Reply via email to