This knowledge about java.vendor strings encoded in a javavendors.xml is unfortunately at the heart of how module jvmfwk works internally. I'm looking into changing that at least for current master (towards LO 6.3), so that jvmfwk assumes that a JRE with a java.vendor not listed in javavendors.xml can be used by LO.
This knowledge about java.vendor strings encoded in a javavendors.xml is unfortunately at the heart of how module jvmfwk works internally. I'm looking into changing that at least for current master (towards LO 6.3), so that jvmfwk assumes that a JRE with a java.vendor not listed in javavendors.xml can be used by LO.