New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multiple JAVA_HOME detected and wrong one selected #1855
Comments
|
Is your repository using codeql? If so, can you include your full (redacted) workflow file? If it isn't using codeql, then this is not the correct repo to raise the issue. |
|
I just learned that we have recently made some changes to CodeQL's ability to discover which versions of Java are installed in the build environment. Please see the details in this issue and it may help with what you are seeing. |
|
Hi @onacit! The issue that @aeisenberg linked to is likely what you are running into, but we have made some further improvements to the version selection logic since. I note that you are currently using CodeQL 2.14.1. CodeQL 2.14.3 contains the improvements, so if you can give that version a go and report back whether that works for you, that would be great! |
|
I think this is still happening: https://github.com/maevsi/android/actions/runs/6648225427/job/18064934351#step:4:78 |


I set up JDK 17 like this.
And it seems that autobuild selects wrong JDK.
And this is my enforcer rules evaluates.
The text was updated successfully, but these errors were encountered: