We did workaround at https://github.com/checkstyle/checkstyle/pull/18253/files to reproduce following issue, we need to revert such update.
The Semaphore 2.0 CI pipeline is consistently failing the Eclipse Static Analysis validation step (.ci/validation.sh eclipse-static-analysis) for a multitude of PRs. ( Example1 , Example2)
The build script compares the supported options of the downloaded eclipse compiler version against config/org.eclipse.jdt.core.prefs.
The latest compiler version introduces the key org.eclipse.jdt.core.compiler.problem.memberOfDeprecatedTypeNotDeprecated, causing the validation check to fail when this key is missing from the configuration file.
This issue is currently blocking all active Pull Requests that run this validation step.
As mentioned in logs as such:
org.eclipse.jdt.core.compiler.problem.invalidJavadocTagsNotVisibleRef 00:48
org.eclipse.jdt.core.compiler.problem.invalidJavadocTagsVisibility 00:48
org.eclipse.jdt.core.compiler.problem.localVariableHiding 00:48
+org.eclipse.jdt.core.compiler.problem.memberOfDeprecatedTypeNotDeprecated 00:48
org.eclipse.jdt.core.compiler.problem.methodWithConstructorName 00:48
org.eclipse.jdt.core.compiler.problem.missingDefaultCase 00:48
org.eclipse.jdt.core.compiler.problem.missingDeprecatedAnnotation 00:48
please update config/org.eclipse.jdt.core.prefs file
Solution is just to add it into config/org.eclipse.jdt.core.prefs.
We did workaround at https://github.com/checkstyle/checkstyle/pull/18253/files to reproduce following issue, we need to revert such update.
The Semaphore 2.0 CI pipeline is consistently failing the Eclipse Static Analysis validation step (.ci/validation.sh eclipse-static-analysis) for a multitude of PRs. ( Example1 , Example2)
The build script compares the supported options of the downloaded eclipse compiler version against
config/org.eclipse.jdt.core.prefs.The latest compiler version introduces the key
org.eclipse.jdt.core.compiler.problem.memberOfDeprecatedTypeNotDeprecated, causing the validation check to fail when this key is missing from the configuration file.This issue is currently blocking all active Pull Requests that run this validation step.
As mentioned in logs as such:
Solution is just to add it into config/org.eclipse.jdt.core.prefs.