Return-Path: Delivered-To: apmail-ant-user-archive@www.apache.org Received: (qmail 65236 invoked from network); 25 Mar 2008 15:02:53 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 25 Mar 2008 15:02:53 -0000 Received: (qmail 98503 invoked by uid 500); 25 Mar 2008 15:02:48 -0000 Delivered-To: apmail-ant-user-archive@ant.apache.org Received: (qmail 98472 invoked by uid 500); 25 Mar 2008 15:02:48 -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 98461 invoked by uid 99); 25 Mar 2008 15:02:48 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Mar 2008 08:02:48 -0700 X-ASF-Spam-Status: No, hits=-2.0 required=10.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [192.85.154.80] (HELO ahmler6.mail.eds.com) (192.85.154.80) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Mar 2008 15:01:56 +0000 Received: from ahmlir5.mail.eds.com (ahmlir5-2.mail.eds.com [192.85.154.135]) by ahmler6.mail.eds.com (8.14.2/8.13.8) with ESMTP id m2PF2Gnw019924 for ; Tue, 25 Mar 2008 11:02:16 -0400 Received: from ahmlir5.mail.eds.com (localhost [127.0.0.1]) by ahmlir5.mail.eds.com (8.13.8/8.12.10) with ESMTP id m2PF29iG028806 for ; Tue, 25 Mar 2008 11:02:09 -0400 Received: from usahm016.amer.corp.eds.com ([130.175.198.26]) by ahmlir5.mail.eds.com (8.13.8/8.12.10) with ESMTP id m2PF293U028797 for ; Tue, 25 Mar 2008 11:02:09 -0400 X-EDSINT-Source-Ip: 130.175.198.26 Received: from camkm231.amer.corp.eds.com ([159.249.31.217]) by usahm016.amer.corp.eds.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 25 Mar 2008 11:02:09 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C88E89.32A95BDA" Subject: Custom Task: Property File argument Date: Tue, 25 Mar 2008 11:02:08 -0400 Message-ID: <8D8DC68827474542ABC749A5656004A0018AA87B@CAMKM231> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Custom Task: Property File argument Thread-Index: AciOiTIAiHXykjxqTkC0Vkg0lLiU3Q== From: "Hache, Martin" To: X-OriginalArrivalTime: 25 Mar 2008 15:02:09.0526 (UTC) FILETIME=[32DFF160:01C88E89] X-Virus-Checked: Checked by ClamAV on apache.org ------_=_NextPart_001_01C88E89.32A95BDA Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I'm writing a Custom Ant Task that needs to act on the properties in a Property File (and just in that property file). So I'm passing my custom task the name of this Property file. I use a java.io.File and a java.io.Properties collection to load this file but I've just now realized that variables in the property file are not being resolved. So, I think that I'm doing this wrong... What's the right way to load a Property file into a custom Ant task to obtain the resolution. I looked into using the Ant Property task within my custom task but it would appear to add the properties to the Ant Project and leave me with no way to reference just the properties in my file. Lastly, this needs to work in Ant 1.6.5 and 1.7 Thanks, Martin. ------_=_NextPart_001_01C88E89.32A95BDA--