+1 on removing the magic property and making it a <jspc> attribute.
The main reason the javac magic property exists is so that you don't have to
specify the compiler for every <javac>, right? Its unlikely that someone
would have a whole lot of <jspc> tasks in their build file so it shouldn't
be too big of an issue, and besides, they can always do
compiler="${jspc.compiler}".
Erik
----- Original Message -----
From: "Steve Loughran" <[EMAIL PROTECTED]>
To: "ant-dev" <[EMAIL PROTECTED]>
Sent: Thursday, March 07, 2002 3:21 AM
Subject: jspc and magic compiler attribute
> <jspc> has a magic compiler property, jsp.compiler, though with only one
> implementation it is unimportant right now
>
>
> 1. Should this task have a magic compiler property, or should it be with a
> compiler attribute as well/instead
> (me: +1)
>
> 2. if there is a compiler attribute, can we pull the magic property
> completely
> (me: +1)
>
> 3. If we do retain the magic property, can I rename it ant.jspc.compiler
> (me: +1 but only if we keep the property)
>
> Probablility of anyone using this property is in the nearly zero category;
> it was in there as the tasks were based on javac...
>
>
> .
>
>
> --
> To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
>
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
