title: Slf4j: Found slf4j-api dependency but no providers were found
body: <p>I use Lombok.
  Some time ago when building a project, the compiler started issuing the following message:</p>
  
  <blockquote>
    <p>Found slf4j-api dependency but no providers were found.  Did you mean
    to add slf4j-simple? See <a href="https://www.slf4j.org/codes.html#noProviders" rel="noreferrer">https://www.slf4j.org/codes.html#noProviders</a>
    .</p>
  </blockquote>
  
  <p>If you follow the link, there is a rather vague comment:</p>
  
  <blockquote>
    <p>This warning, i.e. not an error, message is reported when no SLF4J
    providers could be found on the class path. Placing one (and only one)
    of slf4j-nop.jar slf4j-simple.jar, slf4j-log4j12.jar, slf4j-jdk14.jar
    or logback-classic.jar on the class path should solve the problem.
    Note that these providers must target slf4j-api 1.8 or later.</p>
    
    <p>In the absence of a provider, SLF4J will default to a no-operation
    (NOP) logger provider.</p>
    
    <p>Please note that slf4j-api version 1.8.x and later use the
    ServiceLoader mechanism. Earlier versions relied on the static binder
    mechanism which is no longer honored by slf4j-api. Please read the FAQ
    entry What has changed in SLF4J version 1.8.0? for further important
    details.</p>
    
    <p>If you are responsible for packaging an application and do not care
    about logging, then placing slf4j-nop.jar on the class path of your
    application will get rid of this warning message. Note that embedded
    components such as libraries or frameworks should not declare a
    dependency on any SLF4J providers but only depend on slf4j-api. When a
    library declares a compile-time dependency on a SLF4J provider, it
    imposes that provider on the end-user, thus negating SLF4J's purpose.</p>
  </blockquote>
  
  <p>I have no idea how to do it correctly. If you have an experience, please, explain me how to do it.</p>