Uploaded image for project: 'SLF4J'
  1. SLF4J
  2. SLF4J-570

Feature-request: add a "warningsAsErrors" options.

    XMLWordPrintable

Details

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Minor Minor
    • None
    • 2.0.3
    • Core API

    Description

      Would like to have an API warningAsErrors(Boolean) AND system property `slf4j.warningsAsErrors=true` that turns this report into a failure (throws an exception)

       

       

      SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/Users/me/.gradle/caches/modules-2/files-2.1/io.gitlab.arturbosch.detekt/detekt-formatting/1.21.0/b7e14d2040b8c6092227a0sdf223e9fc54a6/detekt-formatting-1.21.0.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/Users/me/.gradle/caches/modules-2/files-2.1/org.slf4j/slf4j-nop/1.7.36/a3c1eb685d5sdf4527faa93cae311c184032/slf4j-nop-1.7.36.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [org.slf4j.helpers.NOPLoggerFactory]

       

      the API should take precedence over the system property. 

       

      This would allows us to prevent merging of changes that cause issues with our SLF4J bindings. 

       

       

      Attachments

        Activity

          People

            slf4j-dev SLF4J developers list
            yogurtearl Michael Bailey
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: