ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Erik Hatcher" <>
Subject Re: Property Precedence
Date Tue, 20 Nov 2001 11:15:35 GMT

This is really an ant-user question, but I'll go ahead and reply here.
Really the only rule is that properties are immutable and cannot be changed
after they have been set.  Setting a property on the command-line takes
ultimate precedence (with -Dprop=val), and from then on its the order of
property setting in your build.xml that counts.

[There are a few notable exceptions with regards to property setting.  See
<available>, <condition>, <ant>, and <antcall> - but these all have
good reasons for doing what they do]

The rules of properties won't change in Ant 1.x - so you have no worries at
this point of things changing.

If you pose a more concrete example of what is not working properly for you,
on ant-user please, you'll very likely find that its not quite as complex as
you think!  :)


----- Original Message -----
From: "Walker Joe" <>
To: "'Ant Developers List'" <>
Sent: Tuesday, November 20, 2001 6:05 AM
Subject: Property Precedence

> If more than one thing sets a property, the rules as to which value is
> seem to be complex and undocumented.
> I want to have build.xml files which are not generally modified, but that
> can be customised using a properties file. This can't be done easily with
> the complex and undocumented property precedence rules.
> Have I just not looked hard enough?
> Should I dig into the code and write documentation?
> There seemed to be some idea some time ago that the rules surrounding
> property where about to change is this still the case - am I wasting my
> time?
> Joe.
> Legal Disclaimer:-
> Internet communications are not secure and therefore the
> Barclays Group does not accept legal responsibility for the
> contents of this message.  Although the Barclays Group
> operates anti-virus programmes, it does not accept
> responsibility for any damage whatsoever that is caused
> by viruses being passed.  Any views or opinions presented
> are solely those of the author and do not necessarily
> represent those of the Barclays Group.
> Replies to this e-mail may be monitored by the Barclays
> Group for operational or business reasons.
> --
> To unsubscribe, e-mail:   <>
> For additional commands, e-mail: <>

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message