Return-Path: Delivered-To: apmail-jakarta-ant-user-archive@apache.org Received: (qmail 78277 invoked from network); 26 Feb 2002 01:04:03 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 26 Feb 2002 01:04:03 -0000 Received: (qmail 11851 invoked by uid 97); 26 Feb 2002 01:04:01 -0000 Delivered-To: qmlist-jakarta-archive-ant-user@jakarta.apache.org Received: (qmail 11835 invoked by uid 97); 26 Feb 2002 01:04:00 -0000 Mailing-List: contact ant-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Ant Users List" Reply-To: "Ant Users List" Delivered-To: mailing list ant-user@jakarta.apache.org Received: (qmail 11824 invoked from network); 26 Feb 2002 01:04:00 -0000 Message-ID: <040101c1be61$74f59040$6601a8c0@darden.virginia.edu> From: "Erik Hatcher" To: "Ant Users List" References: <00a801c1be49$9e852320$c2a16dc2@operdeck> Subject: Re: How to use hierarchical property files? Date: Mon, 25 Feb 2002 20:03:51 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Reverse the order of your statements. As strange as that sounds, thats how to do it. Properties are immutable so once set they cannot be changed. Load the highest priority ones first. You seem to suggest this solution yourself, so I'm not sure what the issue really is. But this is how its done. Erik ----- Original Message ----- From: "Otto Perdeck" To: "Ant Users List" Sent: Monday, February 25, 2002 5:13 PM Subject: How to use hierarchical property files? Hello, I'd like to be able to use a hierarchical set of optional property files to set up the properties of my project, e.g.: 0. default properties 1. OS family specific properties, if existing, overriding the previously set props 2. OS specfic properties, same 3. host specific properties, same 4. user specific properties, same Simple as this might seem, I could not manage to do this with Ant alone. Somehow, using etc. doesn't work, because every new "" seems to reset ALL properties?! I would *expect* it to just load another set of properties on top of the existing set. I would *like* it to override the existing values, but I appreciate that Ant props are immutable - but this could easily be overcome by reversing the order of loading. I now use an external program (in Java, of course) to "cat" all the given files together, making one large property file. What am I doing wrong? I can't imagine Ant doesn't support something like this. Thanks, -Otto Perdeck -- To unsubscribe, e-mail: For additional commands, e-mail: