refactor: Remove custom JavaProject cache#432
Merged
Conversation
d29b9dc to
1c6d996
Compare
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
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.
I've seen some test failure with the error message:
I don't think, caching these instances is the correct way. If JavaCore.create() is slow, then the caching should happen in eclipse framework, and not in the PMD plugin itself.
The difference is: The cache might contain a project, whose dependent projects are closed, which could result in wrong analysis. JavaCore.create() opens all dependent projects as a side-effect.
The test failure happens only sporadically. So - if with this change all other tests work find, I'll just merge this PR.