On Tue, 2009-09-22 at 11:50 +0200, Hans Dockter wrote: [ . . . ] > The other's are transitive dependencies. For example jsch is used by > Ivy and Ivy determines the version it wants.
I had understood that there was a policy for the Gradle build of not
relying on automated transitive dependencies, but explicitly mentioning
all dependencies in the build files. This means every jar version needs
tracking.
> > BTW Ant 1.7.0 is out of date not up to date, I have amended that
> > entry.
>
> It is up to date for our purposes. Please read the description on the
> wiki page for this dependency.
Sorry but this is a bit of sophistry. The term "up to date" means using
the latest full release issued by the authors. Ant is at 1.7.1, so
Gradle is not using an up to date version. The fact that Gradle has
problems with 1.7.1 where it doesn't with 1.7.0 is not a rationale for
trying to redefine the term up to date.
Was the change 1.7.0 -> 1.7.1 that caused Gradle difficulties a bug
introduced in
Ant or a fixed bug the consequence of which has not been traced and
corrected in Gradle? The words mention JUnit problems, the question is
whether the problem is systemic in Gradle or just a choice not to deal
with it for the moment.
> > Isn't it bizarre that Gradle uses both Commons CLI and JOpt Simple.
>
> Again. This is a transitive dependency issue. commons-cli is used by
> some other first level dependency. I have to check which one and
> whether it is really needed.
Groovyc requires it -- which is why sticking with Commons CLI rather
than switching to JOpt Simple would have not increased the number of
jars depended on. Too late now though.
--
Russel.
=============================================================================
Dr Russel Winder Partner
xmpp: rus...@russel.org.uk
Concertant LLP t: +44 20 7585 2200, +44 20 7193 9203
41 Buckmaster Road, f: +44 8700 516 084 voip: sip:russel.win...@ekiga.net
London SW11 1EN, UK m: +44 7770 465 077 skype: russel_winder
signature.asc
Description: This is a digitally signed message part
