Approach #1 is in fact what I ended up doing. (Actually, I used the
"available" task, not the generalized "condition" task. But the result
was the same.) It wasn't aesthetically pleasing, but it worked. Any time
you have a dummy directory sitting around, you know there's been a hack,
don't
I thought of this, actually. But what puzzles me is how to leverage the
value of "mod_classdir.check", once it has been set (or not set), inside
my path defnition. I could, conceivably, have two path definitions, one
which includes the offendiring fileset, and another which does not,, and
the
That's a clever hack, but it won't work well in my situation, since some
of the filesets may be rooted in directories that cannot be created.
Wouldn't it be nice if the tag had an attribute that allowed you
do say, "It's OK if it doesn't exist"? Something like this:
...
Anyone else have a go
I am constructing a classpath that includes a fileset. Sometimes, the
base directory for that fileset does not exist. I would like Ant to
simply accept this as an empty fileset and move on. Instead, Ant quits
with an error, complaining that the directory is not found. How should I
resolve t
