Thanks Peter will give that a try. We've did up the heap that doesn't seem to be the issue. I think Windows has a hard limit that we're hitting.
Dave On Wed, Jan 26, 2011 at 8:15 AM, Peter Niederwieser <[email protected]> wrote: > > By default, groovyc is run in a forked JVM. I guess the class path that > Gradle passes might get too long. Try: > gradle clean build -d | grep -A 50 > 'org.codehaus.groovy.tools.FileSystemCompiler' > > If this confirms my assumption, feel free to raise an issue against Gradle. > It puts too much on the compile class path currently. > > Meanwhile, you can try to run groovyc in the same JVM: > > [compileGroovy, compileTestGroovy]*.groovyOptions.fork = false > > You might have to raise the heap limit for the Gradle JVM: > > export GRADLE_OPTS=-Xmx512m > > Hope this helps. > > -- > Peter Niederwieser > Developer, Gradle > http://www.gradle.org > Trainer & Consultant, Gradle Inc. > http://www.gradle.biz > Founder, Spock Framework > http://spockframework.org > -- > View this message in context: > http://gradle.1045684.n5.nabble.com/Groovyc-fork-failing-on-Windows-tp3357060p3358039.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 > > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
