On 20/02/10 11:22 PM, Russel Winder wrote:
I think there is a blocking problem with Groovy using Ant 1.8.0 and other Groovy-based systems using Ant 1.7.0 or Ant 1.7.1 -- in this particular instance Gradle. Ants 1.7.1 and 1.7.0 were mutually compatible, but both are seemingly incompatible with Ant 1.8.0. I am getting problems with systems tests that instantiate Ant. Expectations are being calculated using the Groovy Ant (1.8.0) but reality is being provided by the system installed Ant (1.7.1 in my case) and so I am getting differences which are actually spurious but nonetheless terminal. More importantly though is that Gradle is putting some Ant 1.8.0 jars on the class path and some Ant 1.7.0 jars on the classpath. Difficulties do not arise at compile time, but they become seriously apparent at test time. Tests that should pass don't even get run.
Gradle used to do this for tests. It doesn't any more - that was the whole point of reworking the test execution. Are you using a recent build?
Everything gets even worse when trying to execute due to API incompatibilities.
Does 'trying to execute' mean 'trying to execute tests' or something else?
For the moment, this incompatibility of Ant versions leaves Gradle completely useless for managing any project that makes use of Ant :-( I shall experiment further and hopefully will be able to hack something by manually replacing jars in installed applications, but on the face of it all my demonstrations for JAX London on Wednesday are completely ######.
-- Adam Murdoch Gradle Developer http://www.gradle.org --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
