Uploaded image for project: 'Java Driver'
  1. Java Driver
  2. JAVA-5240

Update slf4j-api dependency to 2.0.x

    • Type: Icon: Improvement Improvement
    • Resolution: Won't Do
    • Priority: Icon: Unknown Unknown
    • None
    • Affects Version/s: None
    • Component/s: Build
    • None
    • Hide

      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?

      Show
      1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?

      SLF4J 2.0 was released in August 2022, and Logback 3.0+ now depends on it. By depending on slf4j-api 1.7.x, the driver creates a transitive dependency that conflicts and possibly overrides the dependency in newer Logback releases. While this is easy to work around by excluding the driver's dependency, it does create friction as more and more applications upgrade their logging provider.

      We should consider upgrading our dependency to slf4j-api 2.0.x. This should be safe as all SLF4J releases are binary compatible with each other.

            Assignee:
            Unassigned Unassigned
            Reporter:
            jeff.yemin@mongodb.com Jeffrey Yemin
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: