Paul, On Sun, 2010-02-21 at 12:00 +1000, Paul King wrote: > Hi Russel, does Gradle have an option to exclude the ant runtime? > Or do you currently have java.class.path included in your classpath? > Both are normally considered bad form, e.g. to make GroovyDoc (when > called from Ant 1.7.1) not have issues with Ant 1.8.0 I simply had > to remove java.class.path from the path that the groovydoc task was > using. See here: > > http://fisheye.codehaus.org/changelog/groovy/trunk/groovy/groovy-core?cs=19276
I am not sure to be honest. What I can say is that ant-1.8.0 is on the
class path due to my dependency list, and ant-nodeps-1.7.0 is on the
class path from Gradle for at least one of the test failures.
This would seen to imply that Gradle is adding things to the class path
that really should not be there.
> In hindsight, having it there was poor style which I probably let
> slip in sometime earlier.
>
> Also, in Ant you would normally do something like:
>
> includeantruntime="false"
Another of the test failures complains about the setting or not of this
property so I guess I am hitting this problem as well :-(
> on any javac or junit tasks. I am still trying to work out the
> equivalent for Gradle. Also, another thing you would consider trying
> if you were using Ant would be to call java tasks with fork="true".
> Again, haven't mapped that to Gradle land yet.
My understanding is that Gradle defaults to this now anyway, so I don't
think this is a problem -- witness the fact that Gant compiles fine.
> If you have your demonstrations for Jax in a repo somewhere I can
> probably slurp it down and try a few things out in parallel to you.
By forcibly installing Ant 1.8.0 from the Apache distribution and
removing all trace of Ant installed via Ubuntu packages (this is Ant
1.7.1) then I can at least compile and run Gant even though the tests
fail.
So now I can confidently state that my Ant and Groovy's Ant are the
same, 1.8.0 and Gradle's Ant is 1.7.0. 1.7.1 is no longer an issue here
and no error messages mention that number. The conflict really is now
between Gradle's use of 1.7.0 and Groovy's use of 1.8.0.
I propose to post two JIRAs:
1. Gradle since it clearly forces its Ant onto the user's tests in some
way and this is inapporpriate.
2. Groovy because its choice of Ant is basically forced on all Groovy
applications -- due to the AntBuilder.
I wonder when Java will sort this nightmare of jar version numbers and
inconsistent APIs. Write Once Run Anywhere -- what a ####### joke. :-(
Anyway, I think I've put the Gant talk to bed, now to do the GPars talk.
--
Russel.
=============================================================================
Dr Russel Winder Partner
xmpp: [email protected]
Concertant LLP t: +44 20 7585 2200, +44 20 7193 9203
41 Buckmaster Road, f: +44 8700 516 084 voip: sip:[email protected]
London SW11 1EN, UK m: +44 7770 465 077 skype: russel_winder
signature.asc
Description: This is a digitally signed message part
