Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support JDK 17 for Pulsar 2.11.0 and later #509

Open
xuanyangyang opened this issue Mar 17, 2023 · 4 comments
Open

Support JDK 17 for Pulsar 2.11.0 and later #509

xuanyangyang opened this issue Mar 17, 2023 · 4 comments

Comments

@xuanyangyang
Copy link

pulsar2.11.0 use jdk17.When is jdk17 supported?

@bpereto
Copy link
Contributor

bpereto commented May 11, 2023

there is no dependency on jdk17?
But you are right, jdk-8 is ancient.

I builded the docker image with FROM openjdk:17-slim-bullseye and needed an extra java opts: JAVA_OPTS: "--add-opens java.base/java.lang=ALL-UNNAMED"

with this setup it works fine.

@tisonkun
Copy link
Member

Yeah. This issue looks like to ask to bump the JDK version to 17 in this project.

You're welcome to submit a patch for doing so, or wait for other volunteer take it over :D

@falser101
Copy link

Yeah. This issue looks like to ask to bump the JDK version to 17 in this project.

You're welcome to submit a patch for doing so, or wait for other volunteer take it over :D

What do I need to do if I want to upgrade?@tisonkun

@tisonkun tisonkun changed the title Support pulsar2.11.0 Support JDK 17 for Pulsar 2.11.0 and later Jun 12, 2023
@tisonkun tisonkun mentioned this issue Jun 12, 2023
@onobc
Copy link

onobc commented Feb 2, 2024

This issue came up today at the Pulsar community meeting, in the context of the Pulsar Helm issue w/ a related issue (using older Pulsar client and dependencies).

I would like to bring everything up to the latest dependencies:

  • Spring 6.1.3
  • SpringBoot 3.2.2
  • Pulsar 3.1.2

which implies Java 17.

These changes will warrant a "major" version bump. I see the current version is still < 1.0.0.
We can figure out where the changes land, but likely it would be in a 1.0.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants