Releases: JDiscordBots/NightDream-Logging
fixed bugs where messages but not stacktraces where displayed
Bug fixes
NDSLF4JLogger#*(String,Object,Object) ignored exceptions
If a SLF4J logger method with the parameters String, Object and Object was called and the last object was an exception, the stack trace was not printed before this version.
Low-Level messages with exception passed printed
NDLogger#log(LogType,String,Throwable) logged the text if the log level was too low.
The stack trace was not logged.
correct SLF4J formatting, fixed Win<10
Bug fixes
Win<10
An exception was thrown when initializing NDLogger on a windows version lower than 10.
NightDream-Logging will just log without displaying colors in these versions.
SLF4J MessageFormatter instead of String.format
Previously, NightDream-Logging used String.format for format Strings.
MessageFormatter is used since this release.
SLF4J: fixed default type on format
Bug fixes
fixed default type on format
The SLF4J adapter used LogType.DEFAULT if a format String is logged.
For example, info(String,Object) logged at the default level.
Version 1.0.0
Enum for Logging Types:
io.github.jdiscordbots.nightdream.logging.LogType
The Logger:
io.github.jdiscordbots.nightdream.logging.NDLogger
JCDP-4.0.1
Dependency Updates
JCDP
JCDP is updated from 3.0.0 to 4.0.1.
References
SLF4J trace is LOG level
Bug fixes
The trace level of SLF4J is now logged at the LOG level of NightDream Logging.
Previously, it was logged at the INFO level, which was also used for the SLF4J info level.
Also, the INFO level is logged by default which resulted in a spam of messages by default.
SLF4J Support
Log Level/Module on every line
changes
Log Level/Module on every line
Previously, if a text containing line breaks is logged, the logging level was logged at the first line and the module after the last line of the text.
Since this release, it the log level and the module will be displayed at every line.
JCDP-3.0.0
Dependency Updates
JCDP
JCDP is updated from 2.0.3.1 to 3.0.0.
This does not change the JCDP API or the functionality but the sub-dependencies Jansi and Hamcrest.
References
timestamps at end of line
Bug fixes
timestamps on every print
Timestamps are appended (if activated) at the end of each log output (after the module).
Previously, it was located at every call of com.diogonunes.jcdp.color.ColoredPrinter#print.