Return-Path: Delivered-To: apmail-repository-archive@www.apache.org Received: (qmail 47319 invoked from network); 20 Nov 2003 01:21:53 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 20 Nov 2003 01:21:53 -0000 Received: (qmail 96742 invoked by uid 500); 20 Nov 2003 01:21:38 -0000 Delivered-To: apmail-repository-archive@apache.org Received: (qmail 96681 invoked by uid 500); 20 Nov 2003 01:21:37 -0000 Mailing-List: contact repository-help@apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: repository@apache.org Delivered-To: mailing list repository@apache.org Received: (qmail 96662 invoked from network); 20 Nov 2003 01:21:37 -0000 Received: from unknown (HELO mail.netspace.net.au) (203.10.110.71) by daedalus.apache.org with SMTP; 20 Nov 2003 01:21:37 -0000 Received: from binky (CPE-203-45-8-11.vic.bigpond.net.au [203.45.8.11]) by mail.netspace.net.au (Postfix) with SMTP id A522B41B54 for ; Thu, 20 Nov 2003 12:21:44 +1100 (EST) Reply-To: From: "Tim Anderson" To: Subject: RE: click through license support? Date: Thu, 20 Nov 2003 12:24:39 +1100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 In-Reply-To: <3FBC04B6.3040503@chalko.com> Importance: Normal X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N I was thinking of something like the following: 1. all artifacts in the repository are real or virtual. 2. real artifacts are hosted in the repository 3. virtual artifacts are not hosted, but refer to the real artifact via: 4. http redirection 5. http redirection requiring processing This group can certainly make statements about [1]-[4], as they are language and platform neutral. However, for the java space, [5] is perhaps the most useful. I would like it to be part of the scope for this group, to enable compatibility between tools. E.g, given the URI: http://repo.apache.org/sun/jndi/jars/jndi-1.2.1.jar a tool would automagically go to the Sun website, prompt the user to accept the license, download the jndi-1_2_1.zip distribtion and extract the jar. In terms of implementation, this could be done via redirection to a descriptor containing instructions for obtaining the real artifact. This descriptor might consist of: . the URL of the real artifact . licensing requirements . processing requirements to: . extract the artifact E.g, if the artifact is part of a larger distribution, how to extract it from that distribution. . massage the artifact E.g, renaming the artifact, or changing MANIFEST.MF Class-Path entries to use repository naming conventions. The meta data required to support this are language and platform specific. However, I think it should be easier to form a concensus on the meta-data requirements and format to support this than for other meta-data proposals which are more to do with artifact description than artifact resolution. -Tim > -----Original Message----- > From: Nick Chalko [mailto:nick@chalko.com] > Sent: Thursday, 20 November 2003 11:03 AM > To: repository@apache.org > Subject: Re: click through license support? > > > Tim Anderson wrote: > > >This group could make recommendations as to how > >virtual artifacts could be supported. > > > > > > > > Agree that we should deal with license issue's and virutal artifacts > when we take on metadata.