-
Notifications
You must be signed in to change notification settings - Fork 3.7k
Closed
Labels
release/blockerIndicate the PR or issue that should block the release until it gets resolvedIndicate the PR or issue that should block the release until it gets resolvedtype/bugThe PR fixed a bug or issue reported a bugThe PR fixed a bug or issue reported a bug
Description
Search before reporting
- I searched in the issues and found nothing similar.
Read release policy
- I understand that unsupported versions don't get bug fixes. I will attempt to reproduce the issue on a supported version of Pulsar client and Pulsar broker.
User environment
Client 4.0.6.
Issue Description
Pulsar client 4.0.5 works well with Java 8. Once upgraded to 4.0.6, it errors out, requiring Java 11 to be the minimum version.
Error messages
* What went wrong:
Could not determine the dependencies of task ':example-pulsar-inbound:shadowJar'.
> Could not resolve all dependencies for configuration ':example-pulsar-inbound:runtimeClasspath'.
> Could not resolve com.github.ben-manes.caffeine:caffeine:2.9.1.
Required by:
project :example-pulsar-inbound > org.apache.pulsar:pulsar-client-admin:4.0.6
> Dependency resolution is looking for a library compatible with JVM runtime version 8, but 'com.github.ben-manes.caffeine:caffeine:3.1.1' is only compatible with JVM runtime version 11 or newer.
> Could not resolve com.github.ben-manes.caffeine:caffeine:3.1.1.
Required by:
project :example-pulsar-inbound > org.apache.pulsar:pulsar-client-admin:4.0.6 > io.prometheus:simpleclient_caffeine:0.16.0
> Dependency resolution is looking for a library compatible with JVM runtime version 8, but 'com.github.ben-manes.caffeine:caffeine:3.1.1' is only compatible with JVM runtime version 11 or newer.
* Try:
> Change the dependency on 'com.github.ben-manes.caffeine:caffeine:3.1.1' to an earlier version that supports JVM runtime version 8.
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
> Get more help at https://help.gradle.org.
Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
For more on this, please refer to https://docs.gradle.org/8.14.2/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation.
Reproducing the issue
Try on any project using Java 8.
Additional information
This is a breaking change in the patch version. It should have worked on Java 8 prior to version 4.1.x as per https://github.com/apache/pulsar/blob/master/pip/pip-421.md
Are you willing to submit a PR?
- I'm willing to submit a PR!
Metadata
Metadata
Assignees
Labels
release/blockerIndicate the PR or issue that should block the release until it gets resolvedIndicate the PR or issue that should block the release until it gets resolvedtype/bugThe PR fixed a bug or issue reported a bugThe PR fixed a bug or issue reported a bug