What steps will reproduce the problem?
1. Create an ant build where the instinct task is taskdef(ined) prior to
the specification classes being compiled.
2. Execute the ant target
What is the expected output? What do you see instead?
Expected: All specifications run, as the task should use the nested
classpath provided, and not the classpath used for the taskdef
Actual: The specifications are not found and nothing is executed.
Original issue reported on code.google.com by jem.maw...@gmail.com on 19 Nov 2008 at 10:07
Original issue reported on code.google.com by
jem.maw...@gmail.com
on 19 Nov 2008 at 10:07