feat: add configurable full JAR build mode for complete IDE experience#15
Merged
monkey666-cr merged 2 commits intoMay 14, 2026
Merged
Conversation
…lti-strategy chain Merge separate target_jars and target_source_jars maps into a single ResolvedJar struct that pairs each classpath JAR with its source attachment. Introduce build_resolved_jars() with a 6-strategy resolution chain: class_to_source, interface_to_source, source_by_dir, single_source, infer_source, convention_probe, and maven_cache fallback. Key changes: - Add ResolvedJar struct pairing classpath_path with source_path - Remove get_target_source_jar() in favor of per-jar source_path - Filter stub source JARs (< 1KB) and probe ~/.m2 as fallback - Deduplicate classpath entries and merge source from later targets - Add placeholder native libs in debug build script for bnd validation - Enable bazel_graph=info logging for source resolution diagnostics Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Add a sync mode setting (fast/full) that controls whether the Bazel aspect build requests full JARs or header JARs. In full mode, a new `intellij-resolve-java-full-jars` output group builds transitive runtime JARs, resolving missing imports and InlayHint errors caused by hjars stripping private members. The JAR selection logic now checks file existence before using full JARs, falling back to compile_jars (hjars) when the full JAR hasn't been built. This ensures correct classpath entries regardless of which sync mode was used. Data flow: VS Code `bazel-jdt.syncMode` setting → Java BazelBridge → JNI → Rust `build_with_aspects_sync(full_jars: bool)` → Bazel `--output_groups` flag. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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
2 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.
Summary
bazel-jdt.syncModesetting (fast/full) that controls whether Bazel aspect builds request full JARs or header JARsintellij-resolve-java-full-jarsoutput group builds transitive runtime JARs, resolving missing imports and InlayHint errors caused by hjars stripping private membersChanges
intellij-resolve-java-full-jarsoutput groupfull_jarsflag through JNI layer--output_groupsflag selection based on sync modebazel-jdt.syncModeconfiguration settingData Flow
VS Code
bazel-jdt.syncModesetting → Java BazelBridge → JNI → Rustbuild_with_aspects_sync(full_jars: bool)→ Bazel--output_groupsflagTest plan
🤖 Generated with Claude Code