: Perhaps this is an argument for including JUnit or using ivy? : http://www.nabble.com/Using-ivy-for-dependency-management--tf4396476.html#a12536854
Even if we used a dependency management tool, the junit/ant integration still requires that developers have the ant-junit bindings (aka: ant-junit.jar) in the class path when the build.xml is parsed. supposedly you can explicitly declare the junit tasks with your own taskdef and identify the location of the jars yourself) but the jars still have to exist when that taskdef is evaluated -- which makes it hard to then pull those jars as part of a target. Everybody i've ever talked to who i felt confident knew more about ant then me (with Erik at teh top of the list) has said the same thing: "Put junit and ant-junit in your ANT_LIB ... don't even try to do anything else, it will just burn you." -Hoss
