-
Notifications
You must be signed in to change notification settings - Fork 312
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
Exclude jcl-over-slf4j in favor of Spring Framework's spring-jcl #1191
Comments
Thanks for bringing this up. We have also other places like MongoDB and JPA that use mixed logging strategies and we need to clean up all of these to use Spring's JCL. |
Care to help me understand which dependency you want to exclude? According to
|
Sorry for the lack of details. I noticed the problem when working on Spring Boot 2.4.x and it would appear that it is specific to Spring Data Cassandra 3.1.x:
|
Thanks a lot. |
I'm surprised that 3.1.x has reached OSS EOL already. It's part of Spring Boot 2.4.x which is supported until August 2022. |
@snicoll's just pointed out that I've mixed up my OSS support and full EOL dates. Boot 2.4.x will reach the end of its OSS support period when we release 2.6.0 later this week. We're all good here. |
This is out of support so closing the ticket. |
To avoid having two different variants of the
org.apache.commons.logging
classes on the classpath,jcl-over-slf4j
should be excluded as a transitive dependency. It's present at the moment as it's a transitive dependency ofcom.datastax.oss:java-driver-core
.The text was updated successfully, but these errors were encountered: