[
https://issues.apache.org/jira/browse/CASSANDRA-2785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072864#comment-13072864
]
Hudson commented on CASSANDRA-2785:
-----------------------------------
Integrated in Cassandra-0.8 #243 (See
[https://builds.apache.org/job/Cassandra-0.8/243/])
honor path to java when JAVA_HOME set
Patch by Paul Cannon; reviewed by eevans for CASSANDRA-2785
eevans : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1152241
Files :
* /cassandra/branches/cassandra-0.8/conf/cassandra-env.sh
* /cassandra/branches/cassandra-0.8/debian/cassandra.postinst
* /cassandra/branches/cassandra-0.8/debian/init
* /cassandra/branches/cassandra-0.8/bin/cassandra
> should export JAVA variable in the bin/cassandra and use that in the
> cassandra-env.sh when check for the java version
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-2785
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2785
> Project: Cassandra
> Issue Type: Bug
> Reporter: Jackson Chung
> Assignee: paul cannon
> Attachments: 0001-use-JAVA-in-cassandra-env.sh.patch.txt,
> 0002-fix-usage-of-bash-n-tests.patch.txt
>
>
> I forgot which jira we add this java -version check in the cassandra-env.sh
> (for adding jamm to the javaagent), but we should probably use the variable
> JAVA set in bin/cassandra (will need export) and use $JAVA instead of "java"
> in the cassandra-env.sh
> In a situation where JAVA_HOME may have been properly set as the Sun's java
> but the PATH still have the OpenJDK's java in front, the check will fail to
> add the jamm.jar, even though the cassandra jvm is properly started via the
> Sun's java.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
