On 13/07/2011, at 11:59 AM, Levi Yourchuck wrote: > As it turns out I could not reproduce it with your .zip either, so I started > adding more to the gradle script until I got to my whole script and it still > was fine! > Then I started poking around in the fordeployment folder and saw that I had a > groovy-all.1.5.7 jar in my fordeployments/lib folder, and I had been setting > the classpath for the compileJava and compileGroovy to include **/*.jar from > that folder.
Is there any reason you are doing this rather than using Gradle's dependency management features? That's also a *very* old version of Groovy. > I am assuming though that I ought to still leave the groovy jar on the > compileJava classpath? > I think it is needed since the .java code uses GroovyScriptEngine. Correct, but you should prefer using external dependency management instead of embedding the jar in your build. -- Luke Daley Principal Engineer, Gradleware http://gradleware.com --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
