Dominique Devienne wrote:
The fact that the meaning of was overloaded in the past doesn't
mean we should continue doing so... And still, available currently looks for
files/streams (on file-system, classpath, path, etc...), which is quite
different than looking for particular characteristic of wha
;, you're welcome to write
the parser for it ;-)
--DD
> -Original Message-
> From: J.Pietschmann [mailto:[EMAIL PROTECTED]
> Sent: Thursday, May 15, 2003 1:49 PM
> To: Ant Developers List
> Subject: Re: Testing for an abstract method
>
> Stefan Bodewig wrote:
>
Stefan Bodewig wrote:
Any chance to get the task a bit extended so
that it can also be used to check for methods, fields,
implemented interfaces etc. and specific properties...
>
Doesn't sound too hard. I wouldn't augment available with it but
rather create a new condition, though.
Any suggestion
classes on
the classpath... --DD
> -Original Message-
> From: Stefan Bodewig [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, May 14, 2003 1:00 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Testing for an abstract method
>
> On Tue, 13 May 2003, J. Pietschmann <[EMAIL PROTECTE
On Tue, 13 May 2003, J. Pietschmann <[EMAIL PROTECTED]> wrote:
> Any chance to get the task a bit extended so
> that it can also be used to check for methods, fields,
> implemented interfaces etc. and specific properties, like
> for example
Doesn't sound too hard. I wouldn't augment available w
Could you enter your wish as an enhancement request in Bugzilla.
(http://nagoya.apache.org/bugzilla)
Yours
Antoine
- Original Message -
From: "J.Pietschmann" <[EMAIL PROTECTED]>
To: "Ant Developers List" <[EMAIL PROTECTED]>
Sent: Tuesday, May 13, 2003
Hi all,
over at FOP we have an odd requirement: We are subclassing an
AWT class which got an abstract method added in JDK 1.4.
Unfortunately, the return value class exists in JDK 1.4 only
too, so that generally adding a dummy method still wouldn't
compile on JDK 1.3. The current solutions is to che
