[jira] Commented: (AVRO-566) test_tools.sh should do something intelligent if JAVA_HOME is not set

["Doug Cutting (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AVRO-566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12876300#action_12876300 ] 

Doug Cutting commented on AVRO-566:
-----------------------------------

I think the bug is that build.xml does not bind JAVA_HOME.

We should add a line to the test_tools.sh invocation like:

 <env key="JAVA_HOME" value="${java.home}"/>

Then it will use the same java as Ant, normally the value of JAVA_HOME.  If you want to trust the 'java' on $PATH (which on Ubuntu is OpenJDK or GCJ, depending on Ubuntu version) then Ant will use that, but things might break, since most use Sun JDK 6 for development and in production.  If we want to test for an explicit Java version, we should do it in build.xml though, not in test_tools.sh.


> test_tools.sh should do something intelligent if JAVA_HOME is not set
> ---------------------------------------------------------------------
>
>                 Key: AVRO-566
>                 URL: https://issues.apache.org/jira/browse/AVRO-566
>             Project: Avro
>          Issue Type: Wish
>          Components: java
>            Reporter: Jeff Hammerbacher
>
> Currently, test_tools.sh will fail if the JAVA_HOME environment variable is not set, even if there is a java on the PATH. I generally trust Philip on testing, but I've been bitten a few times by this requirement while trying to build a release. It's low priority, but if it doesn't violate anyone's test-related sensibilities, I'd love to have this test just run with the first "java" it finds on the path if JAVA_HOME is not set.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.