[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
[13:21:54 CDT(-0500)] <EricDalquist> so it could be a little weird running unit tests in eclipse
[13:21:54 CDT(-0500)] <jwennmacher> Is there a way to force the sl4j jars earlier in the classpath?
[13:22:04 CDT(-0500)] <EricDalquist> not sure
[13:22:14 CDT(-0500)] <EricDalquist> I don't know exactly how the m2e plugin orders the classpath
[13:23:21 CDT(-0500)] <jwennmacher> I'll glance at that ... I don't run eclipse though so I'll have someone who does sanity check it. I'll do one portlet first for now.