Try to build with JDK 17-ea

[KengoTODA]

17-ea build 24 now contains support for the Pattern Matching for switch (preview), so I want to confirm how SpotBugs reacts on it.

I just worry that it may reproduce a previous problem at JDK 11 b7, #756 in our issues.
Java 11 changed a way to generate bytecode for try-with-resources and it affects SpotBugs, JaCoCo, and other tools. It's better to confirm the behavior by Early Access build before the GA for the coming LTS.

note: Gradle now uses Groovy 3.0.7, that depends on ObjectWeb ASM 9.0 which doesn't support JDK 17.
I guess we need to bump up the Groovy to 3.0.8 with this change, but not sure how at this moment.
If the build in GitHub Actions failed, I will contact Gradle community to grasp how.

Update: posted to Gradle Community Slack

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[KengoTODA]

It seems JEP 406 isn't ready in the current 17-ea (build 24):
https://github.com/spotbugs/spotbugs/pull/1561/checks?check_run_id=2723285422#step:8:417

/home/runner/work/spotbugs/spotbugs/spotbugsTestCases/src/java14/PatternMatchingForSwitch.java:19: error: : or -> expected

            case Integer i -> String.format("int %d", i);
                        ^
/home/runner/work/spotbugs/spotbugs/spotbugsTestCases/src/java14/PatternMatchingForSwitch.java:19: error: not a statement
            case Integer i -> String.format("int %d", i);
                         ^

I will wait for the coming EA release.

[KengoTODA]

note: I've confirmed that JEP 306: Restore Always-Strict Floating-Point Semantics does not affect SpotBugs detectors. There is no logic related to strictfp, except for IClassConstants.ACC_STRICT. There is no code depending on this IClassConstants.ACC_STRICT.

[KengoTODA]

The build 26 contains enough feature to build switch with pattern match. 🎉