Skip to content

feat: Add configuration-based control for Bazel Java integration#1

Open
runchen0919 wants to merge 1 commit intodevelopfrom
forbidden-loaded-no-java-workspace
Open

feat: Add configuration-based control for Bazel Java integration#1
runchen0919 wants to merge 1 commit intodevelopfrom
forbidden-loaded-no-java-workspace

Conversation

@runchen0919
Copy link
Owner

Implement a mechanism to enable/disable Bazel Java support via a .vscode/.bazel-java-enabled configuration file. The file is written by the VS Code extension and read by JDTLS during project import.

Key features:

  • Check configuration file in applies() method before project import
  • Wait up to 500ms for config file to handle startup race conditions
  • Delete config file after reading to ensure clean state
  • Default to enabled if file doesn't exist or errors occur

This allows the VS Code extension to control when Bazel Java integration should be activated based on user settings.

Implement a mechanism to enable/disable Bazel Java support via a
.vscode/.bazel-java-enabled configuration file. The file is written
by the VS Code extension and read by JDTLS during project import.

Key features:
- Check configuration file in applies() method before project import
- Wait up to 500ms for config file to handle startup race conditions
- Delete config file after reading to ensure clean state
- Default to enabled if file doesn't exist or errors occur

This allows the VS Code extension to control when Bazel Java
integration should be activated based on user settings.
@runchen0919 runchen0919 marked this pull request as ready for review March 2, 2026 03:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant