Taking the opportunity, I made a small change in the code, in the part of the prepare () function, where it is planned to locate and assemble the JAVA_HOME path.
Original
# Avoid the use of any Java 15, actually incompatible with the build
for _java_version in $(archlinux-java status | tail -n +2 | cut -d' ' -f 3 | grep -v 'java-15')
do
export JAVA_HOME="/usr/lib/jvm/${_java_version}"
done
Commited
# Avoid the use of any Java 15, actually incompatible with the build
export JAVA_HOME="/usr/lib/jvm/$(archlinux-java status | tail -n +2 | cut -d' ' -f 3 | grep -v 'java-15' -m 1)"
In environments with multiple JDK installations, the listing returned by exiting thegrep command will contain several options. Like for example:
$ archlinux-java status
Available Java environments:
java-11-openjdk (default)
java-15-openjdk
java-8-openjdk
As suggested, the returned list will always be ordered from the largest version to the smallest, with the version 15-openjdk removed from the list due to incompatibility.
Remembering that currently to compile the project it is suggested to use version 11 of the JDK
Update dbeaver community edition to v.7.3.4
Taking the opportunity, I made a small change in the code, in the part of the
prepare ()
function, where it is planned to locate and assemble the JAVA_HOME path.Original
Commited
In environments with multiple
JDK
installations, the listing returned by exiting thegrep
command will contain several options. Like for example:As suggested, the returned list will always be ordered from the largest version to the smallest, with the version
15-openjdk
removed from the list due to incompatibility.