Sure:
https://docs.gradle.org/6.0-rc-1/userguide/dependency_capability_conflict.html
On 11/2/19 5:27 AM, Ceki wrote:
Hi Marshall,
Any references to those unfamiliar with Gradle “capabilities” mechanism?
--
Ceki Gülcü
On 29.10.2019 17:41, Marshall Pierce wrote:
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
_______________________________________________
slf4j-user mailing list
slf4j-user@qos.ch
http://mailman.qos.ch/mailman/listinfo/slf4j-user
_______________________________________________
slf4j-user mailing list
slf4j-user@qos.ch
http://mailman.qos.ch/mailman/listinfo/slf4j-user
_______________________________________________
slf4j-user mailing list
slf4j-user@qos.ch
http://mailman.qos.ch/mailman/listinfo/slf4j-user
