New JAVA for openHAB3 #629

EliasGabrielsson · 2019-08-04T14:09:30Z

There are discussion on updating JAVA for openHAB 3.0 to at least JAVA 11.
openhab/openhab-distro#768

Nothing new really, just update the packages when times come.
Java Zulu are providing 32-bit packages so we don't need to drop support for older RPis.

mstormi · 2020-03-28T17:33:22Z

There have been a number of proposals, issues and pieces of information related to what Java to use in the future such as #805, #766, #729, #723, #714, a number of forum posts such as https://community.openhab.org/t/running-openhab-2-on-openjdk/21443/8?u=benjy and more.

Please move all activities and discussions to https://github.com/orgs/openhab/teams/refocus-ian/discussions/6 to be the central place for discussing the way forward w.r.t. Java provider.

Additionally, to clarify what Java version this will install, when available, the API will prefer downloading a JRE. However, when a JRE is not available it will use a JDK instead. However, when JDK's are installed only the essential binaries are linked to update-alternatives so extra JDK related software is unlinked (i.e. javac). At the moment, Azul appears to only provide JDK builds for ARM platforms so as such, ARM platforms are most often the ones to not get a JRE installed and the resulting installation tends to be a bit larger (~100 MB). One minor inconvenience is that with the current Azul API it does not allow explicitly choosing builds without the JavaFX additional binaries. So at times, the Java version installed will have extra JavaFX binaries. This is usually seen when the architecture being installed is x86 based. Fixes openhab#714 Fixes openhab#723 See Also openhab#629 Signed-off-by: Ethan Dye <mrtops03@gmail.com>

Additionally, to clarify what Java version this will install, when available, the API will prefer downloading a JRE. However, when a JRE is not available it will use a JDK instead. However, when JDK's are installed only the essential binaries are linked to update-alternatives so extra JDK related software is unlinked (i.e. javac). At the moment, Azul appears to only provide JDK builds for ARM platforms and so, as such, ARM platforms are most often the ones to not get a JRE installed and the resulting installation tends to be a bit larger (~100 MB). One minor inconvenience is that with the current Azul API it does not allow explicitly choosing builds without the JavaFX additional binaries. So at times, the Java version installed will have extra JavaFX binaries. This is usually seen when the architecture being installed is x86 based. Fixes openhab#714 Fixes openhab#723 See Also openhab#629 Signed-off-by: Ethan Dye <mrtops03@gmail.com>

* Use Zulu API v1 when upgrading Java Additionally, to clarify what Java version this will install, when available, the API will prefer downloading a JRE. However, when a JRE is not available it will use a JDK instead. However, when JDK's are installed only the essential binaries are linked to update-alternatives so extra JDK related software is unlinked (i.e. javac). At the moment, Azul appears to only provide JDK builds for ARM platforms and so, as such, ARM platforms are most often the ones to not get a JRE installed and the resulting installation tends to be a bit larger (~100 MB). One minor inconvenience is that with the current Azul API it does not allow explicitly choosing builds without the JavaFX additional binaries. So at times, the Java version installed will have extra JavaFX binaries. This is usually seen when the architecture being installed is x86 based. Fixes #714 Fixes #723 See Also #629 Signed-off-by: Ethan Dye <mrtops03@gmail.com> * Refuse to install 64-bit JDK on 32-bit OS armv8 builds in theory should work on the RPi3+/RPi4, however the current Raspbian kernel uses a armv7l base which works because armv8 is backwards compatible. However, this has the effect of making the builds targeting aarch64 provided by Azul unable to work on the RPi3+/RPi4. On the other hand, this is not a huge issue as the use of 64-bit Java on low-memory boards brings few benefits and mostly issues. Additionally, this adds checking for other platforms to ensure that the OS is actually 64-bit before trying to install a 64-bit JDK. If the OS is not actually 64-bit the installer defaults to installing a 32-bit JDK. Signed-off-by: Ethan Dye <mrtops03@gmail.com>