This repository has been archived by the owner on Aug 5, 2024. It is now read-only.
[fix] prioritize most frequently used JDKs when selecting the project JDK #420
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
abrams27
changed the title
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently JDKs are sorted lexicographically by java home for determinism. Sometimes it can be a problem. when there are 2 JDKs found and one of them is used in nearly all targets and one is used in a few docker related targets that are not relevant. If alphabet is not on your side, you get the wrong JDK (for example wrong architecture) that is not even fetched/resolved fully.
Since JDK resolving is still a heuristic in bazel-bsp, this change should give more useful results usually.