Issue 3244: Checkstyle fails on JDK11 while using Gradle daemon - needs an absolute path #3245
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.
Change log description
The fix is to use an absolute path in order to refer to the suppressions.xml file.
See detailed explanation in #3244
Purpose of the change
Fixes #3244
What the code does
Compute the absolute path during the execution of the build configuration script and do not rely on relative paths
How to verify it
run this command without errors
JAVA_HOME=/path/to/jdk11 ./gradlew checkstyleMain checkstyleTest