Fix #387 - prevent JGit from accessing system config to support Gradle configuration cache #683
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.
As described in the issue - JGit is accessing system config file, which breaks Gradle configuration cache. In order to disable this feature in JGit, we need to supply a new
SystemReader
without this functionality before initializing JGit repository. This newSystemReader
delegates all responsibilities to the original reader, with the exception of loading system config, which is replaced with an empty implementation to prevent access.