fix: create project and refresh classpath for new targets on re-import#31
Merged
monkey666-cr merged 3 commits intoJun 2, 2026
Merged
Conversation
zhirui1994
approved these changes
Jun 2, 2026
zhirui1994
left a comment
zhirui1994
left a comment
There was a problem hiding this comment.
LGTM
Tested it locally，it looks good to me.
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
4 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.
When .bazelproject scope changes, newly added targets ( from new scope ) were discovered but never got Eclipse projects created, leaving them without Java features. Now reimport automatically creates projects for new targets.
After re-importing finish, show hint to ask the user to clean and reload.
Add new scope
Java features work after re-importing
