Downgrade Java version to 17 in .bazelrc#13
Merged
Conversation
Java 21 is still a pretty recent version of Java and could prove to be a barrier to adoption. It looks like the project compiles and runs just fine with Java 17, so I believe we could (and should) lower this as not everyone will be on the latest LTS.
|
|
JamyDev
approved these changes
Sep 2, 2025
24 tasks
JamyDev
pushed a commit
that referenced
this pull request
Sep 8, 2025
## Description A follow-up to #13. This PR changes the Java language level flags defined in `scip_const.py` (as part of the bsp_server) from 21 to 17, to remain consistent with the values defined in `.bazelrc`. ## Type of Change - [x] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] Documentation update - [ ] Refactoring (no functional changes) - [ ] Performance improvement - [x] Test improvement ## Component(s) Affected - [ ] Language Server (ULSP) - [x] SCIP Generation (Python utilities) - [ ] VS Code/Cursor Extension - [ ] Java Aggregator - [ ] Build System (Bazel) - [ ] Documentation - [ ] Tests ## Testing - [ ] I have added tests that prove my fix is effective or that my feature works - [x] New and existing unit tests pass locally with my changes (`bazel test //...`) (<sup>**</sup>see comment) - [x] I have tested this manually with a real project ### Manual Testing Details Describe how you tested these changes: - IDE used for testing: VS Code - Project(s) tested against: Internal company project - Specific features/scenarios verified: run `scip_sync.py` both for a "full" sync an an incremental sync. ## Checklist - [x] My code follows the existing code style and conventions - [x] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [ ] I have updated BUILD.bazel files if I added new source files - [x] My changes generate no new warnings - [x] Any dependent changes have been merged and published ## Screenshots/Logs (if applicable) Include any relevant screenshots, logs, or output that demonstrates the changes. ## Related Issues Fixes #(issue number) Closes #(issue number) Related to #(issue number) ## Additional Notes Any additional information that reviewers should know about this PR.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Description
Java 21 is still a pretty recent version of Java and could prove to be a barrier to adoption. It looks like the project compiles and runs just fine with Java 17, so I believe we could (and should) lower this as not everyone will be on the latest LTS.
Type of Change
Component(s) Affected
Testing
bazel test //...)Manual Testing Details
Describe how you tested these changes:
Checklist
Screenshots/Logs (if applicable)
Include any relevant screenshots, logs, or output that demonstrates the changes.
Related Issues
Fixes #(issue number)
Closes #(issue number)
Related to #(issue number)
Additional Notes
Any additional information that reviewers should know about this PR.