Details
Description
Currently the ant JavaTask used for starting local installed containers defaults to using the JAVA_HOME settings to determine the JVM.
For the project I am currently working on we wanted to be able to specify different JVMs through the cargo configuration by calling through to the setJvm option on the ant task.
The attached patch allows a setting cargo.jvm to be specified. It is assumed to be a JDKsince the tools.jar will be added to the classpath relative to this setting.
Hello David,
I've looked at your patch and I'm wondering if :
Thanks.
Pascal
- o.c.c.c.s.c.AbstractExistingLocalConfigurationCapability.java should be modified too (I'm using an existing configuration)
- these changes are enough (I've applied your patch with some slight modifications but I've not been able to start my existing container with the jdk specified by the cargo.jvm property).
Thanks. Pascal