Chris Riccomini created SAMZA-360:
-------------------------------------
Summary: check-all.sh is not setting JAVA_HOME properly
Key: SAMZA-360
URL: https://issues.apache.org/jira/browse/SAMZA-360
Project: Samza
Issue Type: Bug
Components: build
Affects Versions: 0.8.0
Reporter: Chris Riccomini
Assignee: Chris Riccomini
Fix For: 0.8.0
Attachments: SAMZA-360-0.patch
After using check-all.sh, I noticed that JAVA_HOME is not taking affect with
Gradle. I could tell this because I was getting:
{noformat}
------------- 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]
{noformat}
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.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
