Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

[13:19:32 CDT(-0500)] <jwennmacher> EricDalquist: The SL4J suggests one approach to managing the logging dependencies is to indicate the other logging frameworks are provided (#2 in http://www.slf4j.org/faq.html#excludingJCL). Having gone through the annoying and time-consuming process of doing the exclusions per the best practices suggestions (https://wiki.jasig.org/display/PLT/Logging+Best+Practices) I was wondering if the 'provided' approach would be bette

[13:19:58 CDT(-0500)] <EricDalquist> oh nice

[13:20:04 CDT(-0500)] <EricDalquist> that is much easier

[13:20:06 CDT(-0500)] <EricDalquist> alt2 that is

[13:20:34 CDT(-0500)] <EricDalquist> feel free to update that jasig wiki page with the provided trick

[13:20:46 CDT(-0500)] <jwennmacher> Yes. I'm not sure I fully understand the comment about eclipse still including it on the classpath (an eclipse thing?).

[13:20:53 CDT(-0500)] <jwennmacher> Sounds good. Thanks.

[13:20:58 CDT(-0500)] <EricDalquist> yeah

[13:21:16 CDT(-0500)] <EricDalquist> so eclipse includes "provided" dependencies in the classpath

  • No labels