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

[QOS.CH (JIRA)]

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
------------------------------

Jeremy Landis on 27/Jan/22 1:55 AM
The tools used are not very 'maven' smart.  It doesn't resolve the pom to determine what the license is, it physically looks at the pom and if its not listed, its blocked.  Its not a big deal to me as we already have a CI rewrite to reload4j and notice for any log4j usage but for more widespread usage I'm sure others have this same problem.  As a plus, mavens new central now shows this is relocated but still many are behind corporate domains that don't have direct access and far too many that don't even look in central.  If anything, I'd just suggest adding the license again but otherwise needs no immediate attention.


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