several examples that illustrate both how the rules work and why you want them
to work that way.
The problem is-- these examples exist only in the ant-dev mailing list archives. They
were never turned into real use cases and added to the Ant documentation set. Based on
your question (and the fact that when first starting to use Ant, I had the very same
questions) perhaps it would be worthwhile to do this.
Thoughts?
--Craeg
Walker Joe wrote:
If more than one thing sets a property, the rules as to which value is used 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.
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
