While working with a large source code it often happens that you come across some components which rely on some legacy logging API's rather than slf4j or logback. It's very difficult if not nightmare to keep track of such components and assign appropriate logging level for those components through various configuration files.
The question now arises that is there a way to bridge those legacy logging API to logback ?
Answer is YES.
Logback provides certain jars to do so : http://www.slf4j.org/legacy.html
All the corresponding jars can be downloaded from : http://mvnrepository.com/
The question now arises that is there a way to bridge those legacy logging API to logback ?
Answer is YES.
Logback provides certain jars to do so : http://www.slf4j.org/legacy.html
All the corresponding jars can be downloaded from : http://mvnrepository.com/
IMP : The version of corresponding jars
and the logback jars present in the project should be same.
