[SAMZA-360] check-all.sh is not setting JAVA_HOME properly

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.8.0
• Fix Version/s: 0.8.0
• Component/s: build
• Assignee: Chris Riccomini
• Reporter: Chris Riccomini
• Created: 30/Jul/14 23:45
• Updated: 31/Jul/14 21:48
• Resolved: 31/Jul/14 21:48

Description

After using check-all.sh, I noticed that JAVA_HOME is not taking affect with Gradle. I could tell this because I was getting:

------------- Running check task against JDK6/Scala 2.9.2
....
16:45:03.081 [INFO] [org.gradle.launcher.daemon.client.DefaultDaemonStarter] Starting daemon process: workingDir = /Users/criccomi/.gradle/daemon/2.0, daemonArgs: [/Library/Java/JavaVirtualMachines/jdk1.8.0_11.jdk/Contents/Home/bin/java, -XX:MaxPermSize=512m, -Dfile.encoding=UTF-8, -cp, /Users/criccomi/.gradle/wrapper/dists/gradle-2.0-bin/34ooqmq1urnnhvpv2dlmidjcrc/gradle-2.0/lib/gradle-launcher-2.0.jar, org.gradle.launcher.daemon.bootstrap.GradleDaemon, 2.0, /Users/criccomi/.gradle/daemon, 120000, f9e485f9-6d98-4201-b25c-ba3344d25da8, -XX:MaxPermSize=512m, -Dfile.encoding=UTF-8]

I've also noticed that we test JDK8 against Scala 2.9.2, which won't work, because Scala 2.9.2 doesn't support it.

Lastly, while figuring this out, it would have been nice to be able to do bin/check-all.sh --debug, and have that get forwarded on to Gradle.