Arquillian Managed container always using java command to start the container regardless of JAVA_HOME setting or javaHome property in arquillian.xml

Arquillian Managed container always using java command to start the container regardless of JAVA_HOME setting or javaHome property in arquillian.xml.

This causing problems when one has e.g. openJDK in system PATH variable, but wants to start tests using different Java.

There was also problem with deploying artefacts from tests running Oracle Java 1.6.0_27 and container started using openJDK 1.6.0_20.

19:38:20,112 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) Starting deployment of "sales.war"
19:38:20,258 INFO [org.jboss.as.arquillian] (MSC service thread 1-8) Arquillian deployment detected: ArquillianConfig[service=jboss.arquillian.config."sales.war",unit=sales.war,tests=[org.picketlink.test.integration.saml2.SAML2MixedBindingGlobalLogOutUnitTestCase]]
19:38:20,336 INFO [org.jboss.web] (MSC service thread 1-2) registering web context: /sales
19:38:20,358 INFO [org.jboss.as.server.controller] (pool-1-thread-1) Deployed "sales.war"
19:38:20,368 ERROR [org.jboss.as.controller] (Remoting "hucho:MANAGEMENT" task-2) JBAS014612: Operation ("read-attribute") failed - address: ({
"socket-binding-group" => "standard-sockets",
"socket-binding" => "undefined"
}): org.jboss.msc.service.ServiceNotFoundException: Service service jboss.binding.undefined not found
at org.jboss.msc.service.ServiceContainerImpl.getRequiredService(ServiceContainerImpl.java:447) [jboss-msc-1.0.1.GA.jar:]
at org.jboss.as.server.services.net.BindingMetricHandlers$AbstractBindingMetricsHandler$1.execute(BindingMetricHandlers.java:66) [jboss-as-server-7.1.0.Alpha2-SNAPSHOT.jar:]
at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:322) [jboss-as-controller-7.1.0.Alpha2-SNAPSHOT.jar:]
at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:216) [jboss-as-controller-7.1.0.Alpha2-SNAPSHOT.jar:]
at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:152) [jboss-as-controller-7.1.0.Alpha2-SNAPSHOT.jar:]
at org.jboss.as.server.services.net.BindingMetricHandlers$AbstractBindingMetricsHandler.execute(BindingMetricHandlers.java:76) [jboss-as-server-7.1.0.Alpha2-SNAPSHOT.jar:]
at org.jboss.as.server.services.net.BindingMetricHandlers$BoundAddressHandler.execute(BindingMetricHandlers.java:106) [jboss-as-server-7.1.0.Alpha2-SNAPSHOT.jar:]
at org.jboss.as.controller.operations.global.GlobalOperationHandlers$ReadAttributeHandler.doExecute(GlobalOperationHandlers.java:448) [jboss-as-controller-7.1.0.Alpha2-SNAPSHOT.jar:]
at org.jboss.as.controller.operations.global.GlobalOperationHandlers$AbstractMultiTargetHandler.execute(GlobalOperationHandlers.java:956) [jboss-as-controller-7.1.0.Alpha2-SNAPSHOT.jar:]
at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:322) [jboss-as-controller-7.1.0.Alpha2-SNAPSHOT.jar:]
at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:216) [jboss-as-controller-7.1.0.Alpha2-SNAPSHOT.jar:]
at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:152) [jboss-as-controller-7.1.0.Alpha2-SNAPSHOT.jar:]
at org.jboss.as.controller.ModelControllerImpl$DefaultPrepareStepHandler.execute(ModelControllerImpl.java:426) [jboss-as-controller-7.1.0.Alpha2-SNAPSHOT.jar:]
at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:322) [jboss-as-controller-7.1.0.Alpha2-SNAPSHOT.jar:]
at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:216) [jboss-as-controller-7.1.0.Alpha2-SNAPSHOT.jar:]
at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:152) [jboss-as-controller-7.1.0.Alpha2-SNAPSHOT.jar:]
at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:115) [jboss-as-controller-7.1.0.Alpha2-SNAPSHOT.jar:]
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doProcessRequest(ModelControllerClientOperationHandler.java:158) [jboss-as-controller-7.1.0.Alpha2-SNAPSHOT.jar:]
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.processRequest(ModelControllerClientOperationHandler.java:111) [jboss-as-controller-7.1.0.Alpha2-SNAPSHOT.jar:]
at org.jboss.as.protocol.mgmt.ManagementChannel$RequestReceiver.processRequest(ManagementChannel.java:283) [jboss-as-protocol-7.1.0.Alpha2-SNAPSHOT.jar:]
at org.jboss.as.protocol.mgmt.ManagementChannel$RequestReceiver.access$500(ManagementChannel.java:257) [jboss-as-protocol-7.1.0.Alpha2-SNAPSHOT.jar:]
at org.jboss.as.protocol.mgmt.ManagementChannel.doHandle(ManagementChannel.java:158) [jboss-as-protocol-7.1.0.Alpha2-SNAPSHOT.jar:]
at org.jboss.as.protocol.ProtocolChannel.handleMessage(ProtocolChannel.java:159) [jboss-as-protocol-7.1.0.Alpha2-SNAPSHOT.jar:]
at org.jboss.remoting3.remote.RemoteConnectionChannel$5.run(RemoteConnectionChannel.java:409) [jboss-remoting-3.2.0.CR3.jar:]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.6.0_20]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.6.0_20]
at java.lang.Thread.run(Thread.java:636) [:1.6.0_20]

With my local fix problem disappeared.