Re: What does the repository enable?
Ted Leung wrote: 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 have 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 UNIX 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 http://nagoya.apache.org/wiki/apachewiki.cgi?ASFRepository/Requirements This is a top of my head list of requirements for the Apache Software Repository * ASF Repository shall o only host artifacts approved by a PMC o be accessible to the public via http o be mirrorable. o allow browsing and downloding of artifacts by humans via normal web browser * ASF Repository should o provide metadata about a project, + its components + its dependencies + its artifacts + list of version available + url's to find specific versions of an artifact. o Provide tools for the management of the project metadata o Allow for low cost maintance by hand without tool support. * ASF Repository shall not o Host any artifact in violation of a license, or IPR. Wiki away and add stuff.
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: - To: [EMAIL PROTECTED] 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 have 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 UNIX 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
Re: What does the repository enable?
- Original Message - From: Costin Manolache [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Saturday, March 08, 2003 5:10 PM Subject: Re: What does the repository enable? On Sat, 8 Mar 2003, Ted Leung wrote: 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 2+. Be able to support upgrades/updates ( including checking if any fix is available ) 3. Be able to generate the correct classpath so that a project can run Not sure the repository can generate the classpath - the project should do it. The repository shouldn't make it very difficult to manage the classpath or impose too much pain on the projects. I actually have some code that encodes jar dependencies in the jar manifest, grabs the jars and builds a classpath. It's up at http://www.sauria.com/~twl/code/java/jardeps.jar. I don't care if we use the code or not -- I was just trying to see what would and would not work. Ted
RE: What does the repository enable?
one of the issues with the descriptor approach is bandwidth. This very much depends. Yes - it is overhead (which may be small when well designed) - it may need superfluous TCP opens (when not too well designed) - but it also opens up a whole new set of optimizations, of efficient caching, of trust management, of (partial) mirrors and more ways of avoiding fetching the wrong file as entropy does its usual (and unavoidable) think. So I think that in the long run this trade off may actually be on the bandwidth (or at least perceived latency) side of the coin. Dw
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 have 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 UNIX 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
