ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Arun Gupta <>
Subject RE: Deriving from MatchingTask
Date Thu, 03 Mar 2005 21:27:26 GMT
--- Matt Benson <> wrote:
> --- Dominique Devienne <> wrote:
> [SNIP]
> > Using an implicit fileset is just not as intuitive
> > as
> > using an explicit one, and I recommend you simply
> > derive
> > from Task, and have a
> > add<MyNestedElementName>(FileSet ds)
> > method. Your impl can then accept just one
> filesets,
> > or
> > many, in which case you store then in a List
> > (usually).
I already have a addConfiguredFileset(FileSet fs) in
my task (and able to process them correctly as well)
and currently extends from Task instead of
MatchingTask. But does that mean I cannot have an
"includes" attribute on my task and need to rely upon
the explicit nested filesets only ?

> You would be hard-pressed to find an Ant developer
> who
> does not share this opinion, IMHO.  To put it
> another
> way, please do not derive from MatchingTask!
Can you share the reasoning behind this opinion ?

Lets say I'm a lazy programmer and dont want to
specify nested elements in my task for only one set of
files that needs to be included. I'd rather provide
the option of specifying "includes" attribute as well.
How do I do that with Task ?



Celebrate Yahoo!'s 10th Birthday! 
Yahoo! Netrospective: 100 Moments of the Web

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

View raw message