On Thu, 2009-08-27 at 12:48 -0700, JerodLass wrote: > I might have jumped the gun. I the task actually depends on jdom, jaxen, > jaxen-jdom, and saxpath, and I had put all of them in gradle's lib and the > task ran fine. If I only put jdom in the library, I get errors on the other > dependencies (like saxpath). This means the workaround just got more > intrusive and either jaxen causes classloading problems with jdom and > saxpath or ant.taskdef is still not correctly adding jars to the classpath. > > I haven't had any problems with adding the jars since 45 minutes ago when I > put them in, but is this still an accepted solution to this problem or > should we keep trying to figure out if something else is going wrong?
Personally, I would say that having to put extra jars in the Gradle
installation lib directory indicates a problem: users should never have
to do this.
If you can't get a build working by using Gradle's dependencies, either
in build.gradle or in settings.gradle (whilst that file is still a
player in the game, its deprecated), then Gradle has a bug.
Assuming it is not a Gradle internal feature of course.
--
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
