Xiaojian Ao wrote: > > We can start a jvm and run sonar for one project, when finished we can > exist > the jvm and restart a new jvm to run sonar for next subproject.Running > Sonar > in one subjuect is not dependent any other subproject, so I think this is > a > simple way to work around this issue. >
Forking is an option but would require some work because we integrate with Sonar via its Java API rather than an executable. And once Sonar's API supports multi-projects, we can at most fork one JVM. So I think it's better to profile the Gradle build first and try to understand who's using that much memory. Have you tried to increase the memory limits as I've described? -- 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-tp4411892p4414007.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
