fix: Force JarCache to be on on JarCache tests #5530
Merged
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.
Checklist
Please note that the maintainers will not be reviewing this change until all checkboxes are ticked. See
the Contributions section in the README for more
details.
Discussion thread for this change
Discovered while trying to set up CI for our internal mirror of the plugin.
Description of this change
The combination of running these tests from macOS in bazel doesn't seem to work for these tests, because the
BlazeJavaUserSettings
default touseJarCache=false
when we're not running with Blaze.To solve it, we:
BlazeJavaUserSettings.useJarCache
totrue
, because that's what we're testing.