Use the correct JDK version when indexing Java packages. #215
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
Previously, PackageHub was not able to index Java 11 libraries because it always ran the `index-semanticdb` step on Java 8. Now, we shell out to `cs launch lsif-java --jvm JVM_VERSION` to ensure that the `index-semanticdb` command always uses the correct Java version.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Previously, PackageHub was not able to index Java 11 libraries because
it always ran the
index-semanticdbstep on Java 8. Now, we shell outto
cs launch lsif-java --jvm JVM_VERSIONto ensure that theindex-semanticdbcommand always uses the correct Java version.