Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@apache.org Received: (qmail 50198 invoked from network); 5 Jan 2003 16:03:47 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 5 Jan 2003 16:03:47 -0000 Received: (qmail 29676 invoked by uid 97); 5 Jan 2003 16:05:03 -0000 Delivered-To: qmlist-jakarta-archive-ant-dev@jakarta.apache.org Received: (qmail 29630 invoked by uid 97); 5 Jan 2003 16:05:02 -0000 Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Ant Developers List" Reply-To: "Ant Developers List" Delivered-To: mailing list ant-dev@jakarta.apache.org Received: (qmail 29618 invoked by uid 98); 5 Jan 2003 16:05:02 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) X-Injected-Via-Gmane: http://gmane.org/ To: ant-dev@jakarta.apache.org Path: not-for-mail From: Costin Manolache Subject: Re: Antlib... when? Date: Sun, 05 Jan 2003 07:54:57 -0800 Lines: 64 Message-ID: References: <3E16E83C.9040506@apache.org> <3E16FB37.1050700@cortexebusiness.com.au> <3E177D78.6070208@cortexebusiness.com.au> <3E181BDC.5020404@cortexebusiness.com.au> <3E1835F9.2010706@gmx.de> <3E183A73.9040103@cortexebusiness.com.au> <3E18496D.2050905@apache.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit X-Complaints-To: usenet@main.gmane.org User-Agent: KNode/0.7.1 Sender: news X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Nicola Ken Barozzi wrote: >>> Every JAR in $ANT_HOME/lib would be scanned for a descriptor in >>> META-INF (for example; be it some XML format or a properties file), >>> and that descriptor would contain a URI that needs to be used as XML >>> namespace URI in the build file. >>> >>> Hope I'm not totally off here... haven't followed much of the >>> discussion before this thread. >>> >> >> No, spot on - that is what I had in mind. That's what I had in mind too ( or close enough :-). I was just describing it in reverse - you look in build.xml, see a namespace URI ( or an ) and you locate the descriptor using a resource derived from the URI. JSP are similar - you need to declare all taglibs that you use in the jsp page. Same for XSLT - where all extension elements/functions you use must be declared. One important issue - if you don't have the antlib, you obviously don't have the descriptor either. So the info about where to download must be derived from the URI - either using an indirect catalog or just using the URI as a base for lookup. We can have the URI carry both informations ( descriptor location in the jar and URL for download ) - just use an encoded form of the URL as the resource path. > I think too that this is the way, just with a change: > > - Automatic antlib loads in ant.home/lib would be without namespace, > as they are treated as "default" ones. I think both Conor and me are disagreeing with you on this one. XSLT, JSP, etc are all requiring some explicit information about what antlibs you need - otherwise a user who doesn't have the jars in ant/lib will have no way to guess what is wrong and what .jar he has to install. > - Normal taskdef would be without namespace. I.e backward compat - that's clear. If you mean: you should be able to use taskdef for antlibs - I agree. > - call would be with namespace. Unless is used to load the antlib - which will work like it does today. > As for a descriptor, being a Cocoon developer, and having used xml for > so much time, I can only suggest... not to use it, simple properties > like now is just good enough, just add a namespace property as suggested > above. :-) I agree - keep the simple properties for the simple case ( i.e. what we need today ), and eventually use an XML descriptor for advanced features. Costin -- To unsubscribe, e-mail: For additional commands, e-mail: