If no SLF4J providers are found, SLF4J defaults to no-op logger, which results in all logs, including errors and exceptions being hidden.
IMO this is not a sane default, a better default would be logging exceptions, errors and warning to stdout. stdout is perfectly fine for development and became a common practice for Docker containers in production.
The codebase already has SimpleLogger that does this, but when I tried to reference it in slf4j.LoggerFactory it introduced a circular dependency. Maybe it makes sense to copy SimpleLogger to base package, remove all extra code for configurability/etc, call it FallbackStdoutLogger and use it by default?
If no SLF4J providers are found, SLF4J defaults to no-op logger, which results in all logs, including errors and exceptions being hidden.
IMO this is not a sane default, a better default would be logging exceptions, errors and warning to
stdout.stdoutis perfectly fine for development and became a common practice for Docker containers in production.The codebase already has
SimpleLoggerthat does this, but when I tried to reference it inslf4j.LoggerFactoryit introduced a circular dependency. Maybe it makes sense to copySimpleLoggerto base package, remove all extra code for configurability/etc, call itFallbackStdoutLoggerand use it by default?