[slf4j-dev] [JIRA] Updates for SLF4J-540: Backward compatibility problem with 1.7.34 update

QOS.CH (JIRA) noreply-jira at qos.ch
Tue Jan 25 18:57:00 CET 2022


SLF4J / SLF4J-540 [Open]
Backward compatibility problem with 1.7.34 update

==============================

Here's what changed in this issue in the last few minutes.

There is 1 comment.

View or comment on issue using this link
https://jira.qos.ch/browse/SLF4J-540

==============================
 1 comment
------------------------------

Archie Cobbs on 25/Jan/22 6:44 PM
Like I said, it works if I force the version to {{1.7.34}} (or {{1.7.35}} - just tried that as well).

The problem seems to be that this "loose" version specification no longer works:
{noformat}
<slf4j.version>[1.7,1.8)</slf4j.version>
{noformat}

I don't know how or why Maven is able to choose {{org.slf4j:slf4j-api:jar:1.8.0-beta4:compile}} when the {{${slf4j.version\}}} has an _exclusive_ upper bound of {{1.8}}.

So this seems like more of a Maven problem than an slf4j problem, but either way I don't completely understand it.



==============================
 This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)



More information about the slf4j-dev mailing list