Return-Path: Delivered-To: apmail-ant-user-archive@www.apache.org Received: (qmail 23162 invoked from network); 25 Jan 2007 11:22:37 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 25 Jan 2007 11:22:37 -0000 Received: (qmail 98053 invoked by uid 500); 25 Jan 2007 11:22:41 -0000 Delivered-To: apmail-ant-user-archive@ant.apache.org Received: (qmail 97383 invoked by uid 500); 25 Jan 2007 11:22:39 -0000 Mailing-List: contact user-help@ant.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Ant Users List" Reply-To: "Ant Users List" Delivered-To: mailing list user@ant.apache.org Received: (qmail 97372 invoked by uid 99); 25 Jan 2007 11:22:39 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 Jan 2007 03:22:39 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (herse.apache.org: local policy) Received: from [192.6.10.2] (HELO colossus.hpl.hp.com) (192.6.10.2) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 Jan 2007 03:22:29 -0800 Received: from localhost (localhost.localdomain [127.0.0.1]) by colossus.hpl.hp.com (Postfix) with ESMTP id 564A16BA38 for ; Thu, 25 Jan 2007 11:22:07 +0000 (GMT) X-Virus-Scanned: amavisd-new at hplb.hpl.hp.com Received: from colossus.hpl.hp.com ([127.0.0.1]) by localhost (colossus.hpl.hp.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id O4n7LQRYIBiW for ; Thu, 25 Jan 2007 11:22:06 +0000 (GMT) Received: from ha-node-br2.hpl.hp.com (ha-node-br2.hpl.hp.com [16.25.144.57]) by colossus.hpl.hp.com (Postfix) with ESMTP id 2137B6BA1A for ; Thu, 25 Jan 2007 11:22:04 +0000 (GMT) Received: from [16.25.171.182] (chamonix.hpl.hp.com [16.25.171.182]) by ha-node-br2.hpl.hp.com (8.13.4/8.13.4) with ESMTP id l0PBLqP2005288 for ; Thu, 25 Jan 2007 11:21:52 GMT Message-ID: <45B892D0.6050706@apache.org> Date: Thu, 25 Jan 2007 11:21:52 +0000 From: Steve Loughran User-Agent: Thunderbird 1.5.0.9 (X11/20061206) MIME-Version: 1.0 To: Ant Users List Subject: Re: intra-element attribute property resolution issue References: <1168902419.45ac091403f69@my.visi.com> <45ACB628.8020204@apache.org> <1168990525.45ad613d9dd0b@my.visi.com> <45ADF7D4.8020601@apache.org> <1169048903.45ae4547c98bf@my.visi.com> <7.0.1.0.0.20070117235524.050f00d8@visi.com> <45AF65B6.4070204@apache.org> <7.0.1.0.0.20070118214102.050f01a0@visi.com> <45B4A1CD.6010407@apache.org> <45B4A596.7060307@oopsconsultancy.com> <7.0.1.0.0.20070122233857.058e28a8@visi.com> <45B5F4B3.2080001@apache.org> <7.0.1.0.0.20070123231917.0540cf20@visi.com> <45B73AE7.3050904@apache.org> <20070125012639.260B010FB000@herse.apache.org> In-Reply-To: <20070125012639.260B010FB000@herse.apache.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-HPL-MailScanner-Information: Please contact the ISP for more information X-HPL-MailScanner: Found to be clean X-HPL-MailScanner-From: stevel@apache.org X-Virus-Checked: Checked by ClamAV on apache.org Jacob Kjome wrote: > At 04:54 AM 1/24/2007, you wrote: > >Jacob Kjome wrote: > >> > >> I see your point. Even if the functionality was something you would > >> support, I'm not sure there's anyone willing to put in the time to > >> figure it out. But you never know. Like I said before, it could be an > >> option. So, if someone actually did the work, and it passed rigorous > >> testing, the functionality could be disabled by default and only > enabled > >> explicitly, just like some of the other options of XMLProperty. > > > > > >I'm not sure that I'd put it in xmlproperty. Its more a general purpose > >XML to XML transform; something you'd use to manipulate graphs before > >something like xmlproperty or XSL handles it; something that would have > >a life outside ant. > > > > You mean like transforming attributes to elements, in the desired order > or resolving the property values and placing these resolved values into > the attributes of the same names in the transformed document? yes, and the same for elements. > >> Anyway, it was a good discussion and helped fetter out bugs in AntUnit. > >> BTW, any progress on that? > > > >the bug is filed :) > > > With action soon, I hope. Too bad it was already released as 1.0. This > deficiency makes it useless, IMO. no, all it means is assertions that have a ${something} in their string *and that property is defined* dont work. The rest of the test runner framework works, and I was able to use with nested conditions to get exactly the behaviour I desired. It works, with now one known defect. -steve --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@ant.apache.org For additional commands, e-mail: user-help@ant.apache.org