-
Notifications
You must be signed in to change notification settings - Fork 69
Use pulsar-client-all jar #114
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
Conversation
Hello there, We have just updated to Spring Boot 3.3.3 (3.3.4) while using the Spring Cloud GCP's SecretManager integration, and in the App bootstrap phase we identified a really nasty VerifyError. The problem is that while the GCP dependencies were constantly upgrading the For example in the pulsar-client-all (I guess it's 3.22.3):
And in the 3.25.5 protobuf-java which is used by the Spring Boot GCP dependencies (Secret):
What is the solution?
The question again: Why was it better to include the Error:
|
First of all, let me raise my hand for creating a PR w/ absolutely no description nor motivation for the change. My bad. Let me rectify that now... The need for this change arose when we moved the auto-configuration portion of the project into Spring Boot proper. More details on the Pulsar client libs here: https://pulsar.apache.org/docs/3.3.x/client-libraries-java-setup/#step-1-install-java-client-library So... I did not realize (until now) that protobuf is not being shaded in the current Pulsar client jars (single or all jar). Because of this, even if you use the individual libs you would run into the same issue. Regardless, we would like to improve this situation. I have created and issue to track/communicate on this topic going forward. #876 Thank you very much for taking the time to bring this up again. Much appreciated. |
Hello there @onobc thank you so much, appreciate it. |
@sobychacko