Issue Details (XML | Word | Printable)

Key: CARGO-480
Type: Improvement Improvement
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Adrian Cole
Reporter: Jonas Partner
Votes: 1
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
Cargo

Add configuration option to allow JVM to be specified

Created: 23/Jan/07 09:40 AM   Updated: 07/Dec/08 02:51 PM
Component/s: Core
Affects Version/s: 0.9
Fix Version/s: 1.0

Time Tracking:
Not Specified

File Attachments: 1. Text File cargo-setJVMLocation.patch (3 kB)
2. Zip Archive mylyn-context.zip (106 kB)
3. XML File settings.xml (1.0 kB)


Complexity: Intermediate
Tested on JDKs: 1.4.2_09, 1.5.0_09


 Description  « Hide
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.



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Pascal Thivent added a comment - 11/Mar/07 09:28 AM
Hello David,

I've looked at your patch and I'm wondering if :

  • 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


Adrian Cole added a comment - 07/Dec/08 02:47 PM
example $HOME/.m2/settings.xml that allows running of the following profile, which requires 3 different jdk versions: mvn -Pall-weblogic install

Adrian Cole added a comment - 07/Dec/08 02:51 PM
cargo.java.home can now be set on a standalone or existing local container to assign an alternate JAVA_HOME for the container to use.

samples has been updated to allow support of cargo.<container>.java.home to be provided. These settings can be assigned in your maven $HOME/.m2/settings.xml file