ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Patrick (Gus) Heck" <>
Subject Re: Problems with <import>
Date Thu, 25 Jul 2002 14:51:29 GMT
Yes, but like most style issues it both a question of whether the author
can read it, and whether somebody else can understand it when the author
isn't available for questioning. Also the question is one of speed of
understanding as well. Also, your wording betrays the ease of
misunderstanding. A property used in this way isnt *for a target* it is
for the entire build. It may be that when the property is added it is
only referenced by that target, but then later another target is added
and uses it. Later the original target and the "associated" property are
removed and suddenly the build file breaks... Hopefully it is under CVS
so you can revert and findout what that target was set to... otherwise
you are up a creek without a paddle.

If the target is at the top people are more likely to say... hmm I
wonder what depends on this and search before removing it because there
is no suggestion that it is only used in a single target.


Diane Holt wrote:
> --- "Patrick (Gus) Heck" <> wrote:
> > So as I said before, i am for top level tasks with enforced ordering
> > with targets comming after all initializers if that is possible.
> I don't agree. When I'm cooking something up to provide a solution for
> something asked for on ant-user, I often put the <property> task(s)
> specific to that directly above the <target> for it. I not only don't find
> it confusing -- I do it on purpose.
> Diane
> =====
> (
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Health - Feel better, live better
> --
> To unsubscribe, e-mail:   <>
> For additional commands, e-mail: <>

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

View raw message