Stephan Bergmann
71ee4d75d3
...which appears to be a better fit. Now, gb_JavaClassSet_JAVACDEBUG is unconditionally defined as -g, but conditionally only used if gb_target_symbols_enabled is true for the given target (where the target is spelled "Jar/..." resp. "CustomTarget_jvmfwk/jreproperties" for the --enable-sybmols=... mini-language in configure.ac). Also, the odd special case to "force debug information for OOoRunner" has just been dropped. Change-Id: Ief10efc689d65e2f50888d3e96cb40f43cbb1b2d Reviewed-on: https://gerrit.libreoffice.org/c/core/+/165071 Tested-by: Jenkins Reviewed-by: Stephan Bergmann <stephan.bergmann@allotropia.de>
JVM Framework Wrappers
Wrappers so you can use all the Java Runtime Environments with their slightly incompatible APIs with more ease.
Used to use an over-engineered "plugin" mechanism although there was only one "plugin", called "sunmajor", that handles all possible JREs.
IMPORTANT: The <updated> element in vmfwk/distributions/OpenOfficeorg/javavendors_*.xml files
should only be updated for incompatible changes, not for compatible ones. As stated in the commit
message of https://gerrit.libreoffice.org/#/c/69730/ in LibreOffice gerrit:
javavendors_*.xml <updated> should not have been updated...
Changing <updated> causes jfw_startVM and jfw_getSelectedJRE (both
jvmfwk/source/framework.cxx) to fail with JFW_E_INVALID_SETTINGS, which in turn causes functionality
that requires a JVM to issue a GUI error dialog stating that the user must select a new JRE in the
Options dialog. While that behavior makes sense if a JRE was selected that would no longer be
supported by the modified javavendors_*.xml, it is just annoying if an already selected JRE is still
supported. And a compatible change to javavendors_*.xml implies that an already selected JRE will
still be supported."