Fix gradle command

[ngocnhan-tran1996]

Related gh-5599

I run ./gradlew :micrometer-osgi-test:check and the result is success on my local machine with OS is Windows 11.
I think we should check ./gradlew clean check before merging (maybe the result will be different)

[jonatan-ivanov]

Cannot we "just" upgrade to 7.x instead of using 6.x and 7.x simultaneously?

[shakuzen]

7.x requires Java 17, I believe.

[ngocnhan-tran1996]

@jonatan-ivanov

Java 11 is incompatiable with version 7.x.
It will raise error when build step run.

If just upgrade version, I think we will wait until we have a plan not support prior java 17

[shakuzen]

What's remaining to move this PR to ready for review? I ran ./gradlew check on my machine (Apple M1) and it passed.

[shakuzen]

Just to be clear, this will fix it as long as you are running the build with JDK 17 or higher, but the build will still fail with 11. Is that right?

[ngocnhan-tran1996]

I have not yet tested on java 11. Could we can check via ci/cd?

[shakuzen]

Could we can check via ci/cd?

The CI build uses ./gradlew build, which is also the default task. It'd be good for us to understand what is different when running ./gradlew check vs ./gradlew build. When running the build task, check also gets run as far as I can tell. I really don't get why it fails when the command is check.

[ngocnhan-tran1996]

I confirm it works on java 17

[shakuzen]

Yes, it fixes it when using JDK 17+ with the build, but as far as I could tell ./gradlew check is still broken when using JDK 11 with the build.