ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Erik Hatcher" <jakarta-...@ehatchersolutions.com>
Subject Re: Ant Coding guidelines
Date Sat, 16 Feb 2002 03:30:04 GMT
Why is there even a "magic" property for build.compiler anyway?  Was it just
so you wouldn't have to specify it for every <javac> or something?

I'm +1 on this, but also we should avoid these at almost all costs too.
Although I'm guilty with the MailLogger of using hidden properties, but that
is the only way to configure the darn thing.  I did prefix them with
"MailLogger." though :)

    Erik


----- Original Message -----
From: "Steve Loughran" <steve_l@iseran.com>
To: "Ant Developers List" <ant-dev@jakarta.apache.org>
Sent: Friday, February 15, 2002 7:41 PM
Subject: Re: Ant Coding guidelines


> To quote stephane, "I'm back on the topic of coding guidelines."
>
> We have a few magic properties in the tool, like build.compiler and other
> things, to change system behaviour.
>
> I would like to propose that any more of these we create are prefixed with
a
> well known namespace, like
>
> ant.taskname.
>
> e.g ant.javac.build.compiler
>
> This would ensure that the addition of any new such magic properties would
> not impact any build files which are not using properties in the build
file
> beginning with ant.
>
> This would be the equivalent to the _ prefix in C for runtime functions
and
> variables.
>
> Comments?
>
>
> --
> To unsubscribe, e-mail:   <mailto:ant-dev-unsubscribe@jakarta.apache.org>
> For additional commands, e-mail: <mailto:ant-dev-help@jakarta.apache.org>
>
>


--
To unsubscribe, e-mail:   <mailto:ant-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-dev-help@jakarta.apache.org>


Mime
View raw message