Request: Do not include logback.xml in the library JAR

[joaoseidel]

Description

The library currently includes a logback.xml file inside its packaged JAR. This causes conflicts when applications using the library define their own logging configuration.

Why this is a problem

Including logback.xml in the library results in multiple logging configuration files on the classpath. This can lead to warnings at startup and unpredictable logging behavior, depending on classpath order.

Sample warning:

10:21:38,519 |-WARN in ch.qos.logback.classic.util.DefaultJoranConfigurator@64ec96c6 - Resource [logback.xml] occurs multiple times on the classpath.
10:21:38,519 |-WARN in ch.qos.logback.classic.util.DefaultJoranConfigurator@64ec96c6 - Resource [logback.xml] occurs at [jar:file:/C:/Users/xxx/.gradle/caches/modules-2/files-2.1/io.github.damirdenis-tudor/ktor-server-rabbitmq/1.3.3/669dcaad67867ac496d8f3804b390fc3daffcf50/ktor-server-rabbitmq-1.3.3.jar!/logback.xml]
10:21:38,519 |-WARN in ch.qos.logback.classic.util.DefaultJoranConfigurator@64ec96c6 - Resource [logback.xml] occurs at [file:/E:/dev/xxx/xxx/xxx/build/resources/main/logback.xml]

Suggested Solution

Please remove the logback.xml file from the packaged library. Logging configuration should be left to the consuming application, ensuring it can define its own behavior without conflicts.

[DamirDenis-Tudor]

Good point and great explanation.
I assure you that this mistake was due to a lack of experience. 😄

[joaoseidel]

Good point and great explanation. I assure you that this mistake was due to a lack of experience. 😄

Haha, all good, @DamirDenis-Tudor!
The important thing is that you're open to feedback.