You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Core functionality should be moved from tinylog-api to a new tinylog-core artifact. In tinylog 2, tinylog-api-kotlin, tinylog-api-scala, and tinylog-impl requires tinylog-api as dependency. This leads to some avoidable mistakes of using tinylog. For example, many Kotlin developers import org.tinylog.Logger instead of org.tinylog.kotlin.Logger by accident.
Use standard service loader
tinylog's custom service loader implementation makes trouble when building native images with Graal VM, requires customs rules for ProGuard, and makes it very hard to implement services in Kotlin. Switching to the standard Java service loader would solve these problems. However, this means that builders have to be introduced for all services that require parameters.
Make configuration typesafe compatible
Currently, dirty hacks are requires for using typesafe-config with tinylog as tinylog's writer configurations cannot be translated to YAML. Changing the syntax from writer = <name> to writer.type = <name> would solve this issue.
Convert dynamic path segments into services
In tinylog 2, it is not possible to implement custom dynamic path segments for the rolling file writer.
More formattable types
Currently, tinylog can only format numbers in logging messages. Dates should also be formattable out-of-the-box. Additionally, it would be nice, if custom formatters for additional types could be registered as services.
Align message format and logging format patterns
For message format patterns and logging format patterns, curly brackets should be escaped by single quotes ('). Maybe even the same algorithm could be used for parsing both.
Report invalid properties
A large percentage of questions and bug reports are caused by using configuration properties in the wrong place. To avoid such problems, tinylog 3 could report unsupported properties as a warning when loading the configuration.
Merge all three file writers into one
Currently there are three different file writers: file, shared file, and rolling file. These could be merged into a single file writer to simply the configuration from the user's perspective.
Improve tests
Switch from JUnit 4 to JUnit 5 and write better testable code without using PowerMock.
Multi-release JARs
Migrate to multi-release JARs for supporting legacy Java 8 and modern Java 9+.
Replace tinylog-jul and tinylog-jboss by tinylog-slf4j
All modern web and application servers including Spring Boot should support SLF4J nowadays. Having only a single adapter would simplify the implementation as well as the usage.
The text was updated successfully, but these errors were encountered:
Introduce tinylog-core artifact
Core functionality should be moved from
tinylog-api
to a newtinylog-core
artifact. In tinylog 2,tinylog-api-kotlin
,tinylog-api-scala
, andtinylog-impl
requirestinylog-api
as dependency. This leads to some avoidable mistakes of using tinylog. For example, many Kotlin developers importorg.tinylog.Logger
instead oforg.tinylog.kotlin.Logger
by accident.Use standard service loader
tinylog's custom service loader implementation makes trouble when building native images with Graal VM, requires customs rules for ProGuard, and makes it very hard to implement services in Kotlin. Switching to the standard Java service loader would solve these problems. However, this means that builders have to be introduced for all services that require parameters.
Make configuration typesafe compatible
Currently, dirty hacks are requires for using
typesafe-config
with tinylog as tinylog's writer configurations cannot be translated to YAML. Changing the syntax fromwriter = <name>
towriter.type = <name>
would solve this issue.Convert dynamic path segments into services
In tinylog 2, it is not possible to implement custom dynamic path segments for the rolling file writer.
More formattable types
Currently, tinylog can only format numbers in logging messages. Dates should also be formattable out-of-the-box. Additionally, it would be nice, if custom formatters for additional types could be registered as services.
Align message format and logging format patterns
For message format patterns and logging format patterns, curly brackets should be escaped by single quotes (
'
). Maybe even the same algorithm could be used for parsing both.Report invalid properties
A large percentage of questions and bug reports are caused by using configuration properties in the wrong place. To avoid such problems, tinylog 3 could report unsupported properties as a warning when loading the configuration.
Merge all three file writers into one
Currently there are three different file writers:
file
,shared file
, androlling file
. These could be merged into a single file writer to simply the configuration from the user's perspective.Improve tests
Switch from JUnit 4 to JUnit 5 and write better testable code without using PowerMock.
Multi-release JARs
Migrate to multi-release JARs for supporting legacy Java 8 and modern Java 9+.
Replace tinylog-jul and tinylog-jboss by tinylog-slf4j
All modern web and application servers including Spring Boot should support SLF4J nowadays. Having only a single adapter would simplify the implementation as well as the usage.
The text was updated successfully, but these errors were encountered: