KAFKA-12782: Javadocs search sends you to a non-existent URL

[jlprat]

This is just a workaround to solve this problem while we are still using
JDK11.
Once moving to, presumably, JDK17 this change won't be needed
anymore and could be deleted safely. See https://bugs.openjdk.java.net/browse/JDK-8215291

This change includes a snippet of code copied from JDK 12+

I'm not sure if an extra header needs to be added for the piece of code I copied over, or if I would need to implement it from scratch.

Committer Checklist (excluded from commit message)

• Verify design and implementation
• Verify test coverage and CI build status
• Verify documentation (including upgrade notes)

[jlprat]

cc @ableegoldman as you opened the Jira ticket, maybe you'd like to review this one?

[jlprat]

Test failures were known flaky tests. Added a comment on the corresponding Jira's

[ableegoldman]

To be honest I don't have much context on the javadocs but I will take a look. Maybe @ijuma can help review

[jlprat]

Sure @ableegoldman , no worries. I just mentioned you as you were the one who created the ticket.

[ijuma]

Thanks for looking into this. Can we switch the release requirement to be Java 15 instead of Java 11 then? We can then switch to Java 17 once that's out and stick to that for a while.

[jlprat]

Hi @ijuma, yes, if you would generate the Javadocs with JDK 15 (or 16) instead of 11, it would work (I tried it myself locally). Then one only needs to modify the release.py file to accomplish this.
I could create a PR with those changes if you like.

[ijuma]

Yes, let's go with 15 since Kafka doesn't work with 16 yet.

[jlprat]

Shall, I close this PR and open a new one with the modified release.py?

[ijuma]

Or just replace the code in this branch. Whatever you prefer.

[jlprat]

Closed in favor of #10780