You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Jakob Homan (JIRA)" <ji...@apache.org> on 2015/07/02 06:21:04 UTC

[jira] [Created] (SAMZA-726) Setting JAVA_TOOL_OPTIONS causes bin/check-all to fail

Jakob Homan created SAMZA-726:
---------------------------------

             Summary: Setting JAVA_TOOL_OPTIONS causes bin/check-all to fail
                 Key: SAMZA-726
                 URL: https://issues.apache.org/jira/browse/SAMZA-726
             Project: Samza
          Issue Type: Bug
          Components: build
            Reporter: Jakob Homan
            Priority: Minor


Having JAVA_TOOL_OPTIONS set (to avoid [focus grabbing issues|https://issues.apache.org/jira/browse/HADOOP-10290]) causes the check-all script to fail:
{noformat}iMac 21:17 $ bin/check-all.sh
JAVA6_HOME is not set.
JAVA6_HOME defaulted to /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
JAVA7_HOME is not set.
JAVA7_HOME defaulted to /Library/Java/JavaVirtualMachines/jdk1.7.0_75.jdk/Contents/Home
JAVA8_HOME is not set.
JAVA8_HOME defaulted to /Library/Java/JavaVirtualMachines/jdk1.8.0_40.jdk/Contents/Home
------------- Running check task against JDK6/Scala 2.10/YARN 2.4.0
Picked up JAVA_TOOL_OPTIONS: -Djava.awt.headless=true
To honour the JVM settings for this build a new JVM will be forked. Please consider using the daemon: http://gradle.org/docs/2.0/userguide/gradle_daemon.html.

FAILURE: Build failed with an exception.

* What went wrong:
Could not determine Java version.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.{noformat}
Unsetting the variable allows it to run.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)