Hello Marcus,
I am sure other Ant committers will feel differently. I do not see a
big urge to implement this.
On the other side, why not ?
If you want, open a bug report concerning this idea. Be sure to add
to the bug report source code, documentation and testcases.
New files can be added to the bug report in tar or zip format, for
existing files use svn diff to generate a "patch.txt".
Regards,
Antoine
On Sep 19, 2006, at 2:33 PM, Marcus Lindblom wrote:
Sorry for bouncing. I'm just wondering if there is somewhere (other
than this list) where this is better dicusssed?
/Marcus
Marcus Lindblom wrote:
Hi,
I just want to ask a bit something that probably has been
discussed to death before: unset properties handling. The latest
1.7 does not address this (according to the release notes), and I
could find no enhancement request discussing it either.
So, my simple proposal is:
Allow the user to set a custom handler for resolving properties
(with the option to handle unset properties as errors), similar to
setting build listeners.
We've been running with a modified Ant 1.6.2 for some time that
simply throws an exception if a non-set property is accessed (when
another propery is set, namely ant.disallow_unset_properties). It
works really nice for us and has helped finding quite a few bugs
(that's why we added it in the first place), but a more general
solution would be to provide various property-policies. That way,
I could resolve my other issue (see my recent post) that way as
well, making it a bit more transparent.
Comments?
Cheers,
/Marcus
P.S. I could probably check out 1.7 and make a patch myself, if
you guys think it's worthwhile to include in the future.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
