Even though I think it is not a problem with gradle per se, I was trying to make sense of things by also raising those issues with them:
https://discuss.gradle.org/t/gradle-wants-as-java-version-openjdk-11-even-if-a-newer-version-is-installed/45254 those gradle folks should avail jar files with the latest version of their thing. On 3/28/23, Nicolas George <geo...@nsup.org> wrote: > So what? You expect apt to check the random things installed in your > path? That is not how a package manager works. "random things" you said? Since we are talking here about gradle which is based of groovy, which is just a DSL implementation in java exploiting its reflection API, ... you are not making much sense. Notice that on their installation page: https://gradle.org/install/ they are not telling you that you must have exactly jdk-11. They do state that it must be greater than java version "1.8.0_121" which you check in exactly the way I did; so, it seems that during installation they do check for a java installation in the standard "java -version" way. What I am talking about doesn't exactly relate to what "package managers" do, or so I thought.
