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

[Feature Request]: Upgrade slf4j to v2.0.17 #34107

Closed
1 of 17 tasks
pinfrederic opened this issue Feb 27, 2025 · 3 comments
Closed
1 of 17 tasks

[Feature Request]: Upgrade slf4j to v2.0.17 #34107

pinfrederic opened this issue Feb 27, 2025 · 3 comments

Comments

@pinfrederic
Copy link

What would you like to happen?

Following this ticket: #33574
Can you upgrade slf4j to 2.0.17 instead, because it brings less dependencies, see this link: https://central.sonatype.com/artifact/org.slf4j/slf4j-jdk14/2.0.17/versions

Image

Thanks a lot

Issue Priority

Priority: 2 (default / most feature requests should be filed as P2)

Issue Components

  • Component: Python SDK
  • Component: Java SDK
  • Component: Go SDK
  • Component: Typescript SDK
  • Component: IO connector
  • Component: Beam YAML
  • Component: Beam examples
  • Component: Beam playground
  • Component: Beam katas
  • Component: Website
  • Component: Infrastructure
  • Component: Spark Runner
  • Component: Flink Runner
  • Component: Samza Runner
  • Component: Twister2 Runner
  • Component: Hazelcast Jet Runner
  • Component: Google Cloud Dataflow Runner
@pinfrederic pinfrederic changed the title [Feature Request]: [Feature Request]: Upgrade slf4j to v2.0.17 Feb 27, 2025
@shunping
Copy link
Collaborator

shunping commented Feb 28, 2025

The number of dependencies for 2.0.17 is 3, which is the same as 2.0.16.

I think you mistakenly view the number of packages depending on the slf4j as the number of dependencies.

We just upgraded to 2.0.16, which is not a small step. We will let things settle a bit before moving to the next patch version.

Thanks!

@shunping shunping closed this as not planned Won't fix, can't repro, duplicate, stale Feb 28, 2025
@pinfrederic
Copy link
Author

yes my bad

@shunping
Copy link
Collaborator

yes my bad

No worries :)

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

2 participants