Nicolò Boschi

@codelipenghui This action continue failing in a pull: https://github.com/apache/pulsar/pull/17147 Looking at the [action doc](https://github.com/actions/add-to-project), I see >Note that this action does not support [GitHub projects (classic)](https://docs.github.com/en/issues/organizing-your-work-with-project-boards). And the flaky test...

If it can help, with JDK 17 the `--illegal-access` option does not exist anymore. Currently, the only way to enable PowerMock with JDK 17+ is to add all the --add-opens...

Probably the quickest path is to move the markdown files into the bookkeeper repository.

maybe you need something like this: https://github.com/apache/pulsar/blob/60ef5e983e5e8956bd0b602b5741bd6255c6258a/.github/workflows/ci-unit-broker-client-api.yaml#L86-L99 alternatively, quick and dirty, https://github.com/apache/bookkeeper/blob/1eae5e473b7775419760747b5d1f4dadd0c09052/.github/workflows/backward-compat-tests.yml#L54

perhaps: https://www.githubstatus.com/incidents/fpk08rxnqjz2 can you try to close and reopen the PR ?

@Shoothzj can you look into that ?

Unfortunately most of the Java users are still on JDK8. We must keep the JDK8 compatibility for BK clients. The client and the server are in the same module so...

Anyway, instead of targeting JDK11, I believe we can go with JDK17 and move the CI to JDK17. I did some work on that direction but there's still this issue...

I hit this issue today and I think that there's something to do better. It's a very weird Java API. For example, the ElasticsearchClient could implement Closeable interface and call...

Another one: https://github.com/apache/pulsar/runs/7893473002?check_suite_focus=true