I ran into this with the update to 1.0-milestone3 as well. I'm guessing that
ANT_HOME is not a factor because Gradle is using its own internal ant
dependency to build, not any locally installed ant you might have, and that
with the latest version they've stopped including optional ant jars in that
stack. Whether that's actually true or not I can't confirm right now, but I
can share how I've solved the problem in my build:
configurations {
antClasspath
}
dependencies {
antClasspath 'ant-contrib:ant-contrib:20020829',
'org.apache.ant:ant-junit:1.8.1'
}
// add additional jars to the AntBuilder classpath for use within the
imported build.
ClassLoader antClassLoader = org.apache.tools.ant.Project.class.classLoader
configurations.antClasspath.each { File f ->
antClassLoader.addURL(f.toURI().toURL())
}
--
View this message in context:
http://gradle.1045684.n5.nabble.com/Calling-ant-test-target-fails-with-junit-classpath-issue-newbie-tp4385167p4385795.html
Sent from the gradle-user mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
