Replies: 2 comments 1 reply
-
|
@eleinor Thank you for report. I suggest to analyze the results of "mvn depdency:tree" as well as "mvn help:effective-pom -Dverbose=true" commands. I don't think this is a logback issue. |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
@eleinor Glad to hear that the issue is resolved. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I updated the logback-classic dependency in my project and my archunit tests started to fail with this:
Caused by: java.lang.NoSuchMethodError: 'java.lang.Boolean ch.qos.logback.core.util.OptionHelper.toBooleanObject(java.lang.String)'
I checked the dependencies and I found a weird thing:
[INFO] - ch.qos.logback:logback-classic:jar:1.5.29:test
[INFO] +- ch.qos.logback:logback-core:jar:1.5.25:test (version managed from 1.5.29)
[INFO] - (org.slf4j:slf4j-api:jar:2.0.17:test - version managed from 2.0.17; omitted for duplicate)
Why pulls logback-classic 1.5.29 the logback-core 1.5.25 as a dependency?
If I set logback-core explicitly to the same version, then the issue is resolved. Am I missing something because by mvnrepository it says that logback-classic has logback-core dependency with the same version.
Beta Was this translation helpful? Give feedback.
All reactions