Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@apache.org Received: (qmail 95931 invoked from network); 12 Jul 2002 19:09:45 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 12 Jul 2002 19:09:45 -0000 Received: (qmail 15515 invoked by uid 97); 12 Jul 2002 19:10:00 -0000 Delivered-To: qmlist-jakarta-archive-ant-dev@jakarta.apache.org Received: (qmail 15488 invoked by uid 97); 12 Jul 2002 19:09:59 -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 15470 invoked by uid 98); 12 Jul 2002 19:09:59 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) X-Authentication-Warning: costinm.sfo.covalent.net: costin owned process doing -bs Date: Fri, 12 Jul 2002 12:08:17 -0700 (PDT) From: costinm@covalent.net X-X-Sender: costin@costinm.sfo.covalent.net To: Ant Developers List Subject: Re: My itches for 1.6 In-Reply-To: <3D2F1F5B.2060101@apache.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Fri, 12 Jul 2002, Nicola Ken Barozzi wrote: > > 3. Dynamic properties - i.e. not stored in the Project's Hashtable > > but in a different and configurable source ( like jdk14 prefs, > > xpath expressions on an xml file or jxpath, etc ). That will probably > > be difficult to get accepted into the main branch, but it's worth > > trying :-) > > What's the gain? (ie I don't understand what it means ;-) Right now the properties are stored in a hashtable. Dynamic properties would allow you to do lazy-load of properties from a runtime structure. For example you can speciy an XPath expression on an xml document, or a 1.4 preference ( stored in either the XML or registry ), or an expression in a BSF language. All this by using a special syntax for the property and a hook in the property replacer ( and a global setting to enable this and plug an evaluator ). Accessing the 'prefs' ( either 1.4 or using some application-specific API ) will simplify the integration of ant and reduce the duplication, and hopefully the overuse of properties. Accessing 'live' XML documents using XPath or similar will simplify testing tools like anteater ( and the xml import, etc ). This _doesn't_ mean modifiable properties ( normal properties will remain unmodifiable ), but could be used for this purpose. > -include-import: Nicola Ken + Dominique > http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10276 > > -CVS task that uses netbeans CVS lib: Nicola Ken I'm not making a list of features for 1.6 - it's just my wish list and what I'll like to try to do. I'm +1 on the include-import and I'll also be +1 if antlib ( or a variation based on mutant/myrmidon ) is proposed. Costin -- To unsubscribe, e-mail: For additional commands, e-mail: