public static final void useVerboseConsoleLoggers() {
		String name = LoggerFactory.class.getName();
		LoggerFactory loggerFactory = new ConsoleLoggerFactory(true);
		loggerFactory.getLogger(name).debug("Using Verbose Console logging");
		LOGGER_FACTORY = loggerFactory;
	}
public static final void useVerboseConsoleLoggers() {
		String name = LoggerFactory.class.getName();
		LoggerFactory loggerFactory = new ConsoleLoggerFactory(true);
		loggerFactory.getLogger(name).debug("Using Verbose Console logging");
		LOGGER_FACTORY = loggerFactory;
	}
public static final void useVerboseConsoleLoggers ( ) { String name = LoggerFactory . class . getName ( ) ; LoggerFactory loggerFactory = new ConsoleLoggerFactory ( true ) ; loggerFactory . getLogger ( name ) . debug ( "Using Verbose Console logging" ) ; LOGGER_FACTORY = loggerFactory ; }
Force the usage of Console-based {@link Logger Loggers}, even if SLF4J is available
on the classpath. Console loggers will output {@link Logger#error(String) ERROR} and
{@link Logger#warn(String) WARN} levels to {@link System#err} and levels below to
{@link System#out}. All levels (including TRACE and DEBUG) are considered enabled.
<p>
The previously active logger factory is simply replaced without
any particular clean-up.
Force the usage of Console - based {