[ https://issues.jboss.org/browse/JBIDE-22799?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22799: ------------------------------------ Looks like the slave on which the job is now running DOES have all 4 JDKs available. Here are the 4 Oracle JDKs being used: {code} 13:37:53 + echo jbosstoolstestjre5=/qa/tools/opt/x86_64/jdk1.5.0_last 13:37:53 java version "1.5.0_22" 13:37:53 Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_22-b03) 13:37:53 Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_22-b03, mixed mode) 13:37:53 + echo jbosstoolstestjre6=/qa/tools/opt/x86_64/jdk1.6.0_last 13:37:54 java version "1.6.0_45" 13:37:54 Java(TM) SE Runtime Environment (build 1.6.0_45-b06) 13:37:54 Java HotSpot(TM) 64-Bit Server VM (build 20.45-b01, mixed mode) 13:37:54 + echo jbosstoolstestjre7=/qa/tools/opt/x86_64/jdk1.7.0_last 13:37:55 java version "1.7.0_79" 13:37:55 Java(TM) SE Runtime Environment (build 1.7.0_79-b15) 13:37:55 Java HotSpot(TM) 64-Bit Server VM (build 24.79-b02, mixed mode) 13:37:55 + echo jbosstoolstestjre8=/qa/tools/opt/x86_64/jdk1.8.0_last 13:37:55 java version "1.8.0_121" 13:37:55 Java(TM) SE Runtime Environment (build 1.8.0_121-b13) 13:37:55 Java HotSpot(TM) 64-Bit Server VM (build 25.121-b13, mixed mode){code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)