javaToolchains incorrectly reports 'does not contain a java executable' on Debian and Ubuntu about gradle HOT 6 OPEN

I know it is frustrating, and sorry for an extended answer..

Let's change the abstraction about what this is telling us instead of proving the software is wrong.
The message is actually right, that path does not contain an executable.
Looks like this situation has been created deliberately.

-Edit-
Workaround removed because it wasn't working anymore.
I will investigate a little more

from gradle.

Maybe the 'warning' should be moved to info-level logs?

In the standard situation, the message does not give an end user any useful advice – so should not be visible by default. But info level is quite verbose, it's fine to have this message there.

Changing the log level is easier than tweaking the logic, but while being easy, still will improve user experience.

from gradle.

Hmm its relevance? sure, but...
I wouldn't downplay the importance of this issue in terms of the performance hit when using the resolver.
I'm trying to understand if it's being used every time a task is executed, because it shouldn't .. unless the daemon is down. But even then, while using Gradle in development chances are we are specifying which path to use so in those cases a resolver doesn't seem optimal. Again, unless there is no daemon available, and the path mismatch the desired version.

I just raised this question on Slack as I'm trying to review the flow to understand if this is a mistake on my part (concepts, workflow, something else), or otherwise ask if doing so is really necessary.
I'm not confidence on getting an answer from it because the thread has become long/dense, full of outputs and observations, so I doubt someone will follow to last/recent replies there.

from gradle.