I am sorry, I have missed this thread. I believe that requiring JDK17 to build and especially to RUN the Pulsar broker is not a good idea currently. Many enterprises, especially the bigger, or banks, insurance companies....have strict requirements on some components and they are very slow to accept bleeding edge tecnologie.
I believe that it is good to run CI on JDK17 and also to build the docker images on JDK17. But I know a few companies who won't be able to switch to JDK17 very quickly. I think it is better to require JDK11 at this moment, and not JDK17, otherwise users will be stuck with Pulsar 2.10 for a long time. Requiring JDK17 would be justified only if there is some required new feature, but this is not the case. So I propose to change the required JDK version to build and run to JDK11 for the server part and JDK8 for the client. Enrico Il giorno lun 9 mag 2022 alle ore 12:03 Lari Hotari <lhot...@apache.org> ha scritto: > > PIP-156 PR https://github.com/apache/pulsar/pull/15264 has been merged to > master branch. > > Please notice that Java 17 is now required for building Pulsar master branch. > > btw. https://sdkman.io/ is handy for managing multiple JDK versions in local > development environments. > > -Lari > > > On 2022/04/20 16:37:21 Heesung Sohn wrote: > > Dear Pulsar Community, > > > > Please review and vote on this PIP. > > > > PIP link : https://github.com/apache/pulsar/issues/15207 > > > > Thank you, > > -- > > > > <https://streamnative.io> > > > > Heesung Sohn > > > > Platform Engineer > > > > e: heesung.s...@streamnative.io > > > > streamnative.io > > > > <http://github.com/streamnative> > > <https://www.linkedin.com/company/streamnative/> > > <https://twitter.com/streamnativeio/> > >
