And we got that by binding slf4j to log4j for building. To be able to enable/disable logging per component at build time, to reduce the noise.The flexibility to plug in whatever logging system one would want, and that is achieved by slf4j.How we got to that decision is another story, and it is not the something for this document :-) What we wanted So we looked at log4j (for flexibility), and Apache commons logging (for “swapping” the logger), but in the end we decided to go with slf4j. But as okapi started being used in all kind of other products, both server and desktop, it became more and more necessary to allow for more flexibility, so that we can accommodate the logging in the hosting environment.Īlso, having more flexibility in specifying what to log and what not was also something we would have liked. For a long time the logging in okapi used the.
