SLF4J / SLF4J-592 [Open] Mechanism for indicating provider to use for unit tests.
============================== Here's what changed in this issue in the last few minutes. There are 2 comments. View or comment on issue using this link https://jira.qos.ch/browse/SLF4J-592 ============================== 2 comments ------------------------------ Ceki Gülcü on 21/Jun/23 21:48 [~garretwilson] The provider ordering mechanism would be part of SLF4J. I only mentioned logback configurators as an example for inspiration. In logback 1.4.9 (experimental/unreleased), Configurator implementations declare their priority via an annotation. This annotation is part of the configurator class and cannot be altered without altering the compiled class. This approach might be more rigid than what you may have had in mind but should work assuming you create your own SLF4J providers... A custom provider can potentially consist of only a single class implementing SLF4JServiceProvider having the right order annotation and delegating to an existing implementation such as slf4j-simple. ------------------------------ Garret Wilson on 21/Jun/23 21:53 {quote}The provider ordering mechanism would be part of SLF4J. … This approach might be more rigid than what you may have had in mind but should work assuming you create your own SLF4J providers.{quote} OK that sounds workable. I don't mind publishing a simple {{stdout}} logging provider (or a version of {{slf4j-simple}}) with its priority set high. ============================== This message was sent by Atlassian Jira (v9.6.0#960000-sha1:a3ee8af) _______________________________________________ slf4j-dev mailing list [email protected] https://mailman.qos.ch/cgi-bin/mailman/listinfo/slf4j-dev
