fix: propagate transitive compile deps for non-project jar dependencies#4
Open
runchen0919 wants to merge 1 commit intodevelopfrom
Open
fix: propagate transitive compile deps for non-project jar dependencies#4runchen0919 wants to merge 1 commit intodevelopfrom
runchen0919 wants to merge 1 commit intodevelopfrom
Conversation
When a direct dependency resolves as jars (not an Eclipse project), Eclipse's project-level export mechanism cannot propagate the dependency's own compile-time deps. This causes ECJ to fail resolving types in the dependency's public API (e.g., SpecificRecord for Avro-generated classes). Load the dependency's EXPLICIT jdeps entries and add them as discouraged compile entries so ECJ can resolve the full type chain.
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
1 participant
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.
When a direct dependency resolves as jars (not an Eclipse project), Eclipse's project-level export mechanism cannot propagate the dependency's own compile-time deps. This causes ECJ to fail resolving types in the dependency's public API (e.g., SpecificRecord for Avro-generated classes).
Load the dependency's EXPLICIT jdeps entries and add them as discouraged compile entries so ECJ can resolve the full type chain.