'[slf4j-user] Avoiding SLF4J classpath issues'

[prev in list] [next in list] [prev in thread] [next in thread] 

List:       slf4j-user
Subject:    [slf4j-user] Avoiding SLF4J classpath issues
From:       Marshall Pierce <marshall () mpierce ! org>
Date:       2019-10-29 16:41:13
Message-ID: 860ACA99-B10F-42E1-B067-C2F31419A1CF () mpierce ! org
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]

I made a plugin [1] for Gradle using their new "capabilities" mechanism to make it so \
that common classpath issues (multiple bindings, recursion with incorrect bridge \
setups, etc) are now detected at build time rather than surfacing as odd logging \
behavior at runtime. Let me know if you have ideas for how it could be improved. 

- Marshall

[1] https://plugins.gradle.org/plugin/org.mpierce.slf4j-capabilities

[Attachment #5 (text/html)]

<html><head><meta http-equiv="content-type" content="text/html; \
charset=utf-8"></head><body dir="auto"><div>I made a plugin [1] for Gradle using \
their new "capabilities" mechanism to make it so that common classpath issues \
(multiple bindings, recursion with incorrect bridge setups, etc) are now detected at \
build time rather than surfacing as odd logging behavior at runtime. Let me know if \
you have ideas for how it could be improved.&nbsp;</div><div><br></div><div>- \
Marshall</div><div><br></div>[1]&nbsp;<a \
href="https://plugins.gradle.org/plugin/org.mpierce.slf4j-capabilities">https://plugins.gradle.org/plugin/org.mpierce.slf4j-capabilities</a></body></html>

[Attachment #6 (text/plain)]

_______________________________________________
slf4j-user mailing list
slf4j-user@qos.ch
http://mailman.qos.ch/mailman/listinfo/slf4j-user

[prev in list] [next in list] [prev in thread] [next in thread] 