Return-Path: Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list ant-dev@jakarta.apache.org Received: (qmail 57327 invoked from network); 30 Nov 2000 10:47:04 -0000 Received: from bodewig.bost.de (root@195.227.98.11) by locus.apache.org with SMTP; 30 Nov 2000 10:47:04 -0000 Received: (from bodewig@localhost) by bodewig.bost.de (8.9.3/8.9.3) id LAA02765; Thu, 30 Nov 2000 11:47:04 +0100 X-Authentication-Warning: bodewig.bost.de: bodewig set sender to bodewig@bost.de using -f To: ant-dev@jakarta.apache.org Subject: Re: [PROPOSAL] jar distribution system References: From: Stefan Bodewig Date: 30 Nov 2000 11:47:04 +0100 Message-ID: Lines: 47 User-Agent: Gnus/5.0807 (Gnus v5.8.7) XEmacs/21.1 (Channel Islands) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N Jon Stevens wrote: > I have placed the start of cjan.xml up on the jakarta.apache.org > site > > > Just a quick thought: CJAN (the client side application) needs some way to know whether a given dependency is fulfilled on the local system or not. I see two options here: (1) keep track on all JARs that have ever been loaded and installed in a CJAN registry. This forces the user to install every component which might be available to CJAN through CJAN - I don't think you can expect this on a multi user system, even for single use boxes this seems too strong therefore I'd prefer (2) Add some like functionality. The section describing a product as well as a service (I like Conor's concept) should hold something like ... ... Stefan