The problems of coming back to a system after a period of rapid development . . .
I used to use compile.unmanagedClasspath to put a set of jars from a
known directory into the classpath without using the dependency notation
-- which requires knowing version numbers (*). However a build that
used to work, now gives:
Cause: Could not find method unmanagedClasspath() for arguments
[[/home/users/russel/lib/Java/gradle/lib/jetty-util-6.1.14.jar,
/home/users/russel/lib/Java/gradle/lib/jsch-0.1.31.jar,
/home/users/russel/lib/Java/gradle/lib/ant-junit-1.7.0.jar,
/home/users/russel/lib/Java/gradle/lib/bndlib-0.0.255.jar,
/home/users/russel/lib/Java/gradle/lib/ant-1.7.0.jar,
/home/users/russel/lib/Java/gradle/lib/core-3.1.1.jar,
/home/users/russel/lib/Java/gradle/lib/ant-trax-1.7.0.jar,
/home/users/russel/lib/Java/gradle/lib/ivy-2.1.0-rc2.jar,
/home/users/russel/lib/Java/gradle/lib/maven-ant-tasks-2.0.9.jar,
/home/users/russel/lib/Java/gradle/lib/servlet-api-2.5.jar,
/home/users/russel/lib/Java/gradle/lib/logback-core-0.9.9.jar,
/home/users/russel/lib/Java/gradle/lib/jaxen-1.1.jar,
/home/users/russel/lib/Java/gradle/lib/commons-httpclient-3.0.jar,
/home/users/russel/lib/Java/gradle/lib/ant-nodeps-1.7.0.jar,
/home/users/russel/lib/Java/gradle/lib/groovy-all-1.6.3.jar,
/home/users/russel/lib/Java/gradle/lib/commons-io-1.4.jar,
/home/users/russel/lib/Java/gradle/lib/commons-codec-1.2.jar,
/home/users/russel/lib/Java/gradle/lib/dom4j-1.6.1.jar,
/home/users/russel/lib/Java/gradle/lib/logback-classic-0.9.9.jar,
/home/users/russel/lib/Java/gradle/lib/jopt-simple-2.4.1.jar,
/home/users/russel/lib/Java/gradle/lib/jsp-api-2.1-6.1.14.jar,
/home/users/russel/lib/Java/gradle/lib/jetty-annotations-6.1.14.jar,
/home/users/russel/lib/Java/gradle/lib/junit-4.5.jar,
/home/users/russel/lib/Java/gradle/lib/slf4j-api-1.5.3.jar,
/home/users/russel/lib/Java/gradle/lib/ant-launcher-1.7.0.jar,
/home/users/russel/lib/Java/gradle/lib/commons-lang-2.3.jar,
/home/users/russel/lib/Java/gradle/lib/jetty-6.1.14.jar,
/home/users/russel/lib/Java/gradle/lib/jetty-naming-6.1.14.jar,
/home/users/russel/lib/Java/gradle/lib/gradle-wrapper-0.7-20090717075902+0100.jar,
/home/users/russel/lib/Java/gradle/lib/jcl-over-slf4j-1.5.3.jar,
/home/users/russel/lib/Java/gradle/lib/jetty-plus-6.1.14.jar,
/home/users/russel/lib/Java/gradle/lib/asm-all-2.2.3.jar,
/home/users/russel/lib/Java/gradle/lib/webdavlib-2.0.jar,
/home/users/russel/lib/Java/gradle/lib/gradle-0.7-20090717075902+0100.jar,
/home/users/russel/lib/Java/gradle/lib/jsp-2.1-6.1.14.jar]] on task ':compile'.
So I guess either unmanagedClasspath has changed semantics (page 82 of
the user guide appears to say very little :-( or I am just using it
wrong:
if ( useInstalledGradle ) { compile.unmanagedClasspath ( ( new File (
installedGradleHome ) ).listFiles ( [ accept : { File dir , String name -> (
name =~ '\\.jar$' ).find ( ) } ] as FilenameFilter ) as List ) }
If anyone has any insights to help me get over this, it would be great
to get them.
Thanks.
(*) I don't know whether Maven or Ivy allow this, but as the Maven
repository knows the latest version of a jar in the repository it ought
to be able to offer "the latest version" of an artefact rather than
having to be told which version to get.
--
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
