Java version
25
OS
Doesn't matter, reproducible on MacOS, Win 11, Linux
Architecture
Doesn't matter
Tarantool Java SDK version
1.7.0
Other relevant dependencies and versions
No response
Bug description
Hi,
We found that tarantool-core is packaged with a root-level logback.xml file inside the released JAR.
This causes problems when the Tarantool Java client is used inside a Spring Boot application that already has its own logging configuration, for example logback-spring.xml.
In our case, after adding the Tarantool client dependency, application logging was reset to the default/plain behavior. Our logback-spring.xml was no longer effectively applied: custom console pattern, custom appender/replacement logic, and logger levels stopped working as expected.
The issue is reproducible because Logback discovers the logback.xml from the Tarantool JAR on the application classpath.
Example diagnostic output with Logback status listener enabled:
Could NOT find resource [logback-test.xml]
Found resource [logback.xml] at [jar:file:/.../.m2/repository/io/tarantool/tarantool-core/1.6.0/tarantool-core-1.6.0.jar!/logback.xml]
Dependency path:
io.tarantool:tarantool-client
-> io.tarantool:tarantool-core
Steps to reproduce
See description plz
Expected behavior
A library JAR should not provide a root-level logback.xml, because this file is treated by Logback as an application-level configuration file. Runtime libraries normally should not configure the host application's logging system.
Actual behavior
Our logback-spring.xml was no longer effectively applied: custom console pattern, custom appender/replacement logic, and logger levels stopped working as expected.
Additional context
Suggested fix:
Please remove logback.xml from the published runtime JAR, or move it to test resources if it is only needed for SDK tests/development.
For example:
src/main/resources/logback.xml -> should not be included in runtime artifact
src/test/resources/logback-test.xml -> OK for tests
Current workaround on the application side:
logging:
config: classpath:logback-spring.xml
This workaround forces Spring Boot to use the application logging config, but it would be better if the Tarantool SDK did not include an application-level Logback configuration in the library artifact.
Thanks.
Minimal reproducible example
No response
Java version
25
OS
Doesn't matter, reproducible on MacOS, Win 11, Linux
Architecture
Doesn't matter
Tarantool Java SDK version
1.7.0
Other relevant dependencies and versions
No response
Bug description
Hi,
We found that tarantool-core is packaged with a root-level logback.xml file inside the released JAR.
This causes problems when the Tarantool Java client is used inside a Spring Boot application that already has its own logging configuration, for example logback-spring.xml.
In our case, after adding the Tarantool client dependency, application logging was reset to the default/plain behavior. Our logback-spring.xml was no longer effectively applied: custom console pattern, custom appender/replacement logic, and logger levels stopped working as expected.
The issue is reproducible because Logback discovers the logback.xml from the Tarantool JAR on the application classpath.
Example diagnostic output with Logback status listener enabled:
Could NOT find resource [logback-test.xml]
Found resource [logback.xml] at [jar:file:/.../.m2/repository/io/tarantool/tarantool-core/1.6.0/tarantool-core-1.6.0.jar!/logback.xml]
Dependency path:
io.tarantool:tarantool-client
-> io.tarantool:tarantool-core
Steps to reproduce
See description plz
Expected behavior
A library JAR should not provide a root-level logback.xml, because this file is treated by Logback as an application-level configuration file. Runtime libraries normally should not configure the host application's logging system.
Actual behavior
Our logback-spring.xml was no longer effectively applied: custom console pattern, custom appender/replacement logic, and logger levels stopped working as expected.
Additional context
Suggested fix:
Please remove logback.xml from the published runtime JAR, or move it to test resources if it is only needed for SDK tests/development.
For example:
src/main/resources/logback.xml -> should not be included in runtime artifact
src/test/resources/logback-test.xml -> OK for tests
Current workaround on the application side:
logging:
config: classpath:logback-spring.xml
This workaround forces Spring Boot to use the application logging config, but it would be better if the Tarantool SDK did not include an application-level Logback configuration in the library artifact.
Thanks.
Minimal reproducible example
No response