You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since mixing 2.0.x and 1.7.x slf4j-api versions is not supported (cf. https://www.slf4j.org/faq.html#changesInVersion200), it would be nice if HikariCP could update to a current, stable version of SLF4J.
The text was updated successfully, but these errors were encountered:
Is the reason that this ticket was closed to avoid causing chaos downstream?
Asking because I'm working on converting automatic jars to explicitly modularized ones, and I'm considering just excluding hikari's dependency on slf4j-api:1.x in favor of 2.x, and I'm curious to know if there is some technical reason why hikari does not depend on the newer versions.
Version 2.0.7 of SLF4J was released: https://www.slf4j.org/news.html
The latest released version of HikariCP, version 5.0.1, depends, for Java 11 and newer, on slf4j-api version 2.0.0-alpha1:
https://github.com/brettwooldridge/HikariCP/blob/HikariCP-5.0.1/pom.xml#L555-L566
Since mixing 2.0.x and 1.7.x slf4j-api versions is not supported (cf. https://www.slf4j.org/faq.html#changesInVersion200), it would be nice if HikariCP could update to a current, stable version of SLF4J.
The text was updated successfully, but these errors were encountered: