| Summary: | Installer should find and propose the standard JVM as per the user's PATH | ||
|---|---|---|---|
| Product: | [Tools] Oomph | Reporter: | Stephan Herrmann <stephan.herrmann> |
| Component: | Setup | Assignee: | Ed Merks <Ed.Merks> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | ||
| Version: | 1.1.0 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 465370, 466867 | ||
|
Description
Stephan Herrmann
This is also related to bug 465370. And to bug 466867. This is address by this commit: http://git.eclipse.org/c/oomph/org.eclipse.oomph.git/commit/?id=13bb84027e0aa7a3992c93a9402218cf8c312b8f I.e., the java.home of the running installer will be included as a JRE. It will be the default if it's a valid choice and you've not chosen a different one previously; the dialog remembers the most recent choice. You can remove ~/.eclipse/org.eclipse.oomph.jreinfo/defaults.txt to reset this historical knowledge. I just updated Oomph, removed defaults.txt and then later everything in ~/.eclipse/org.eclipse.oomph.jreinfo/, but still in the Java Virtual Machines dialog I only see a bunch of VMs under "System" (those from the OS), and no mentioning of my default 1.8 VM. How can I find out, which JVM is actually used by Oomph? According to lsof -p, Oomph is accessing a lot of files of the desired 1.8 VM *plus* /usr/lib/jvm/java-7-openjdk-i386/jre/lib/i386/IcedTeaPlugin.so Ah, maybe I should be more patient to wait for the update to appear on my end? Which build do I need in order to get the fix? Restoring previous bug-status while waiting for the update, sorry for the churn ... You should see one of the JREs shown bold in the dialog. This is the one corresponding to java.home of the current running VM. I certainly see that on my Linux box, Mac box and Windows, so there should always be a bold entry and without persisted default, which should be chosen the first time. |