You know, that makes sense *smacks head*. I put it on the back burner
today, but I'll try it in the morning. Thanks!
Bruce Atherton wrote:
The reason is that you have only defined your sets of directories. They
aren't resolved until you use them. Try doing something with the dirset
and see i
The reason is that you have only defined your sets of directories. They
aren't resolved until you use them. Try doing something with the dirset
and see if you get your exception. I used:
classpath="." >
and got:
Buildfile: build.xml
BUILD FAILED
/sand
I'm trying to write a custom selector. It works fine, except that
isSelected is never called. This is using 1.6.5, with the .jar for
the selector in ant's lib directory and the jar contains an
antlib.xml. Here's the pared down version.
Yes, isSelected is set to throw an exception if it's ever ca
obert Rice
> >
> > On Tue, 12 Aug 2003, Dominique Devienne wrote:
> >
> > > I think I spoke too soon...
> > >
> > > You can get back the current Task, thru Project#getThreadTask, but you
> > need
> > > a Project instance to do that. I'm not
rospection rules as for types and tasks, and thus supercedes the
> > Parameter-based stuff.
>
> I have written (enclosed) a manual page (not complete) that attempts to
> describe the introspection method of defining custom conditions
> and custom selectors.
>
> Peter
te that Ant CVS HEAD configures selectors using the same
> introspection rules as for types and tasks, and thus supercedes the
> Parameter-based stuff.
I have written (enclosed) a manual page (not complete) that attempts to
describe the introspection method of defining custom conditions
an
