| Type Params | Return Type | Name and description |
|---|---|---|
|
static java.lang.Object |
configureLogging(ch.qos.logback.classic.Level level, boolean consoleLogEnabled, boolean fileLogEnabled, java.lang.String logFileName, java.lang.String logDir, boolean grettyDebug)Configure a default logging configuration for Gretty. |
|
static java.lang.Object |
configureLoggingWithJoran(java.io.File logbackConfigFile) |
|
static java.lang.Object |
reset() |
|
static java.lang.Object |
setLevel(boolean debugEnabled)Configure Gretty's logging as part of the bootstrap process. |
| Methods inherited from class | Name |
|---|---|
class java.lang.Object |
java.lang.Object#wait(long), java.lang.Object#wait(long, int), java.lang.Object#wait(), java.lang.Object#equals(java.lang.Object), java.lang.Object#toString(), java.lang.Object#hashCode(), java.lang.Object#getClass(), java.lang.Object#notify(), java.lang.Object#notifyAll() |
Configure a default logging configuration for Gretty.
Especially the implementation for the scan interval bases off
ch.qos.logback.classic.gaffer.ConfigurationDelegate.
Additionally, below implementation tries to avoid all pitfalls from
https://stackoverflow.com/a/46121422/345057, in particular:
Configure Gretty's logging as part of the bootstrap process. The very first step after launching the child process consists of configuring the debug level. This will allow Gretty to log diagnostic output before we receive detailed logging configuration (level, file paths, etc.) from the parent process via the network. Having the detailed logging configuration, we proceed to LogUtil.configureLogging.