Xiaojian Ao wrote: > > It seems a bug in gradle ? > Hard to say. Basically all we do is to call the Sonar API. And as far as I can tell, we don't hold on to anything after a subproject has been analyzed. I'll have to look at this in the profiler again.
In order to analyze the whole Gradle project with Sonar (which took about 90 minutes), I used the following memory settings: export GRADLE_OPTS="-Xmx1G -XX:MaxPermSize=512m" As far as I remember, -Xmx512m wasn't enough in this case. -- Peter Niederwieser Principal Engineer, Gradleware http://gradleware.com Creator, Spock Framework http://spockframework.org Blog: http://pniederw.wordpress.com Twitter: @pniederw -- View this message in context: http://gradle.1045684.n5.nabble.com/outofmemory-error-to-execute-sonar-in-multiple-project-env-tp4411892p4412648.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
