ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dominique Devienne <DDevie...@lgc.com>
Subject RE: Testing for an abstract method
Date Wed, 14 May 2003 14:11:57 GMT
And a new selector hopefully... I'd like to select JUnit test cases with
more than just a filename pattern. It's actually on my to-do list, and I
should have it within a few weeks (when I get around to it). We've been
doing it for months with a special Unit test which does it in its suite()
method, and I need to move the code into a selector (although as I stated
before, I hate the kind of extension mechanismSSSS available in Ant 1.5.x).
Note that my current code, and most likely my future selector, will use
regular introspection, and not BCEL, so will need the dependent classes on
the classpath... --DD

> -----Original Message-----
> From: Stefan Bodewig [mailto:bodewig@apache.org]
> Sent: Wednesday, May 14, 2003 1:00 AM
> To: dev@ant.apache.org
> Subject: Re: Testing for an abstract method
> 
> On Tue, 13 May 2003, J. Pietschmann <j3322ptm@yahoo.de> wrote:
> 
> > Any chance to get the <available> 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 with it but
> rather create a new condition, though.
> 
> Stefan

Mime
View raw message