CliArgumentsTestCase should not rely on java beeing on path ------------------------------------------------------------ Key: WFLY-2574 URL: https://issues.jboss.org/browse/WFLY-2574 Project: WildFly Issue Type: Bug Security Level: Public(Everyone can see) Components: CLI, Test Suite Affects Versions: 8.0.0.Beta1 Reporter: Tomaz Cerar Assignee: Alexey Loubyansky Priority: Critical Fix For: 8.0.0.CR1 If there is no java on path tests fail with {noformat} java.lang.AssertionError: Failed to start CLI process: Cannot run program "java": error=2, No such file or directory at org.junit.Assert.fail(Assert.java:88) at org.jboss.as.test.integration.management.cli.CliScriptTestBase.execute(CliScriptTestBase.java:108) at org.jboss.as.test.integration.management.cli.CliScriptTestBase.execute(CliScriptTestBase.java:73) at org.jboss.as.test.integration.management.cli.CliScriptTestBase.execute(CliScriptTestBase.java:69) at org.jboss.as.test.integration.management.cli.CliArgumentsTestCase.testConnectArgument(CliArgumentsTestCase.java:103) {noformat} Test should use JAVA_HOME env variable or java that ran "current" process without this fix it is really hard to properly test build with different JDKs as test will always use default java for executing commands instead of build provided/configured one