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

[fix][client] Remove javax.ws.rs-api dependency from client side #23646

Conversation

lhotari
Copy link
Member

@lhotari lhotari commented Nov 27, 2024

Motivation

Current pulsar-client 4.0.0 pom includes multiple unwanted dependencies.
It contains the javax.ws.rs-api dependency which is a server-side dependency. It should be removed.
This is one of changes required to remove javax dependencies from the shaded Pulsar client, related to #21297.

Modifications

  • move RestException and PoliciesUtil to pulsar-broker-common since they are the classes that depend on javax.ws.rs-api and they aren't needed in client side code.
  • move defaultBundle method to BundlesData
  • remove unnecessary javax.ws.rs-api dependency from pulsar-common module
  • remove unnecessary javax.ws.rs-api dependency from pulsar-client-auth-sasl module

Documentation

  • doc
  • doc-required
  • doc-not-needed
  • doc-complete

…ndencies

- move RestException and PoliciesUtil to pulsar-broker-common since they are the classes that depend on
  javax.ws.rs-api and they aren't needed in client side code.
- move defaultBundle method to BundlesData
@lhotari
Copy link
Member Author

lhotari commented Nov 27, 2024

Closing in favor of #23647 since integration tests fail when the dependency is removed from client side.

@lhotari lhotari closed this Nov 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants