lhotari commented on PR #15264: URL: https://github.com/apache/pulsar/pull/15264#issuecomment-1120955794
> Why are we requiring JDK17 to build ? Initially, the motivation for this was to enable the use of new language features in Pulsar server-side modules, for example, using the Java record types. > > I agree that we can ensure that Pulsar works well on JDK17 and that we should run CI on JDK17. but in many companies it is not allowed to use JDKs that are "too modern." I doubt that it's a problem for Pulsar broker. You must run Pulsar on a recent JDK version in any case, and requiring Java 17 makes sense for the broker. Pulsar client and Pulsar admin client libraries will continue to support Java 8. For some reason, PIP-156 was specified in a way that Pulsar CLI tools also require Java 17 to run. @heesung-sn Can you explain why Java 17 is required for Pulsar CLI tools? > > can we REQUIRE JDK11 instead of JDK17 ? That's possible, but I don't think that there's a specific reason to stop at JDK11 now that JDK17 is the current Java LTS release. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
