I've determined that the root of the issue seemed to be coming from a call to the http://openide.netbeans.org/lookup/ Lookup class buried within some third-party libraries that I use. The Lookup class is making use of the JDK's provider extension mechanism (http://java.sun.com/j2se/1.3/docs/guide/jar/jar.html#Provider%20Configuration%20File). When running within the GroovyShell, the Lookup class was never able to find an implementation, even though a JAR containing it was on the classpath.
As I said, I had this exact problem when trying to run my tool as an Ant task a ways back, so this could easily be something related to Ant. As stated in my other post, I've been able to deal with this by simply doing an Ant java call to run my generator. -- View this message in context: http://www.nabble.com/Classpaths-classloaders-in-Gradle-tp17105685p17146905.html Sent from the gradle-user mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
