[
https://jira.jboss.org/jira/browse/JBAS-6658?page=com.atlassian.jira.plug...
]
Emanuel Muckenhuber commented on JBAS-6658:
-------------------------------------------
Additionally the java.exec property in 'server-config.xml' could also be reviewd?
<!--Default java executable for starting server -->
<property name="java.exec" value="${env.JAVA_HOME}/bin/java"/>
At least it does match the ant script here:
if [ -z "$JAVACMD" ] ; then
if [ -n "$JAVA_HOME" ] ; then
# IBM's JDK on AIX uses strange locations for the executables
if [ -x "$JAVA_HOME/jre/sh/java" ] ; then
JAVACMD="$JAVA_HOME/jre/sh/java"
elif [ -x "$JAVA_HOME/jre/bin/java" ] ; then
JAVACMD="$JAVA_HOME/jre/bin/java"
else
JAVACMD="$JAVA_HOME/bin/java"
fi
else
JAVACMD=`which java 2> /dev/null `
if [ -z "$JAVACMD" ] ; then
JAVACMD=java
fi
fi
fi
testsuite uses wrong jvm to execute junit tests
-----------------------------------------------
Key: JBAS-6658
URL:
https://jira.jboss.org/jira/browse/JBAS-6658
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Test Suite
Affects Versions: JBossAS-5.1.0.Beta1
Reporter: Emanuel Muckenhuber
Assignee: Dimitris Andreadis
Fix For: JBossAS-5.1.0.CR1
Currently forked junit tests are executed with the wrong jvm. It just uses the
'java' from the $PATH. Although the jvm specified in $JAVA_HOME should to be used.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira