That is not what is happening with SLF4J. The nop logger is present in the API artifact. The API artifact chooses to warn when using it. The nop dependency, despite the name, contains no logger at all. It just explicitly forces the usage of the nop logger.
It's pretty clever actually, and works in a straight-forward way.
It's pretty clever actually, and works in a straight-forward way.