Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@apache.org Received: (qmail 99387 invoked from network); 1 Feb 2002 15:40:31 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 1 Feb 2002 15:40:31 -0000 Received: (qmail 15002 invoked by uid 97); 1 Feb 2002 15:40:16 -0000 Delivered-To: qmlist-jakarta-archive-ant-dev@jakarta.apache.org Received: (qmail 14977 invoked by uid 97); 1 Feb 2002 15:40:15 -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 14943 invoked from network); 1 Feb 2002 15:40:15 -0000 Message-ID: <009f01c1ab36$ac64b7b0$6401a8c0@darden.virginia.edu> From: "Erik Hatcher" To: "Ant Users List" Cc: "ant-dev" References: <01c501c1ab07$239bfa30$6401a8c0@darden.virginia.edu> <200202011316.g11DG0R30218@mail004.syd.optusnet.com.au> Subject: Re: Thoughts about properties Date: Fri, 1 Feb 2002 10:39:44 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" 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 Peter, I'm in agreement that this could be a handy patch. I'll actually even take a stab at implementing it! :) Erik ----- Original Message ----- From: "Peter Donald" To: "Ant Users List" Sent: Friday, February 01, 2002 7:02 AM Subject: Re: Thoughts about properties > On Fri, 1 Feb 2002 20:59, Erik Hatcher wrote: > > > 1) Add a '-properties ' to specify a properties file > > > which in effect "globally" for a single ant run. Obviously > > > it's possible to obtain something close to this functionality > > > by inserting the tag at the top of my > > > build file, but if I have my build.xml files set up in a > > > cascading manner (as I do) and want the flexibility to build > > > against any build file in any directory, I have to include the > > > tag in every single build file. And I believe > > > that ant will reload that same properties file with each build.xml it > > > parses, which seems like kind of a waste. > > > > This particular case could be implemented by doing this: > > > > > > > > and then: > > > > ant -Dcommandline.properties.file= > > > > And if that property is not supplied, will not fail, it > > just ignores it. > > > > As for it having to be in every build file... nope. Look at the FAQ and > > using entity reference includes. > > I actually think this may be a good idea ;) We already allow users to define > UserProperties on the command line but doing a bunch of them is cumbersome > and unwieldy. On many occasions you don't always have nicely written build > files who all load properties in a consistent and universsal manner. This is > particularly painful when integrating multiple different projects built by > different people. > > Essentially loading properties file from commandline would be a shortcut. So > instead of goin > > ant -Da=1 -Db=2 -Dc=3 -Dd=4 ... -Dz=26 > > you just go > > ant -propertyfile project.properties > > and project.properties contains > a=1 > b=2 > c=3 > ... > z=26 > > which is much easier to use I guess. > > > -- > Cheers, > > Pete > > ------------------------------------------ > I just hate 'yes' men, don't you Smithers? > ------------------------------------------ > > -- > To unsubscribe, e-mail: > For additional commands, e-mail: > > -- To unsubscribe, e-mail: For additional commands, e-mail: