Return-Path: Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list ant-dev@jakarta.apache.org Received: (qmail 63901 invoked from network); 12 Jan 2001 12:06:01 -0000 Received: from mta02.mail.au.uu.net (HELO mta02.mail.mel.aone.net.au) (203.2.192.82) by h31.sny.collab.net with SMTP; 12 Jan 2001 12:06:01 -0000 Received: from cognetnt ([63.12.2.114]) by mta02.mail.mel.aone.net.au with SMTP id <20010112120558.GRNY6914.mta02.mail.mel.aone.net.au@cognetnt> for ; Fri, 12 Jan 2001 23:05:58 +1100 Message-ID: <02e601c07c90$dc22fff0$80dc1fcb@cognetnt> From: "Conor MacNeill" To: References: Subject: Re: Property substitutions, Contributed Tasks, & New features Date: Fri, 12 Jan 2001 23:11:52 +1100 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 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N > For example, I can say: > > java -Dmysysprop=foo net.x180.foo.Bar > > And my code could override that property. It's ok. Works fine. > I don't find the analogy too compelling. but I assume you mean would not override a command line value, but would? When I am doing a build, I want to be able to control certain properties and not have the build file just ignore them. As the build runner I want priority over the build writer. The build.compiler flag would be a good example, but even build specific properties should be controllable from the command line. To have to edit the build file to change one of those values would be a chore. The same issue comes up with sub-builds. Which build controls the values, parent or child? > -- > James Duncan Davidson duncan@x180.net > !try; do() > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: ant-dev-unsubscribe@jakarta.apache.org > For additional commands, e-mail: ant-dev-help@jakarta.apache.org >