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
Is it intentional to use SLF4J as apposed to commons-logging (as Spring Framework does)? If it is, this doesn't seem ideal given the framework uses commons-logging. We should probably also update the dependencies for #20 to have slf4j an implementation and switch to jcl-over-slf4j
The text was updated successfully, but these errors were encountered:
We used SLF4J in Spring Cloud Vault and so it was retained. Spring Vault isn't very demanding regarding logging so aligning with Spring Framework by using commons-logging seems like natural fit.
Is it intentional to use SLF4J as apposed to commons-logging (as Spring Framework does)? If it is, this doesn't seem ideal given the framework uses commons-logging. We should probably also update the dependencies for #20 to have slf4j an implementation and switch to
jcl-over-slf4j
The text was updated successfully, but these errors were encountered: