On Tue, 26 Sep 2023, olivares33561 via users wrote:
[olivares@fedora mptmp]$ rpm -qa | grep openjdk
java-17-openjdk-headless-17.0.8.0.7-1.fc38.x86_64
java-latest-openjdk-headless-21.0.0.0.35-1.rolling.fc38.x86_64
java-latest-openjdk-21.0.0.0.35-1.rolling.fc38.x86_64
java-latest-openjdk-devel-21.0.0.0.35-1.rolling.fc38.x86_64
[olivares@fedora mptmp]$ javac Ulam.java --release 17
[olivares@fedora mptmp]$ java Ulam
Is there a better way to avoid doing this, ie removing java 17 and
forcing 21 ? or vice versa to avoid this. I had not encountered this before in previous
versions of Fedora it just worked! Now I have to specify. What would be the best thing
to do? and make it work correctly.
I'd expect that within any sensible system,
the java compiler and the java
virtual machine would be compatible.
The package java-17... seems to be an outlier and
seems to be where the java virtual machine is coming from.
If another package has a headless virtual machine,
you might want to get rid of java-17... .
--
Michael hennebry(a)mail.cs.ndsu.NoDak.edu
"Occasionally irrational explanations are required" -- Luke Roman