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 are 2 comments. View or comment on issue using this link https://jira.qos.ch/browse/SLF4J-540 ============================== 2 comments ------------------------------ Jeremy Landis on 25/Jan/22 11:27 PM Try using [1.7.0,1.7.99) for your range instead of what you had. 1.8.0-beta4 is not standard with maven. So its not that surprising that a lessor used feature to relocate artifacts acts in odd ways. Another note on relocation poms, they are sort of useless in most use cases. For example, if you are behind firewalls and have to bring in jars, why would you want to bring in a pom to update? Its confusing at best and not well documented. That is why some relocation poms especially long time ago always had a JAR present so it was just the warning out to the build process. Further, tools like renovate / dependabot don't handle relocations. ------------------------------ Jeremy Landis on 25/Jan/22 11:32 PM One other thing, the relocation pom is missing a license. Even if everyone wanted to use, some cannot due to that fact. I do see some usefulness to the relocation as not everyone got the email notifications but it needs a bit more to be proper for those behind firewalls with systems like synk checking for proper licenses. ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59) _______________________________________________ slf4j-dev mailing list [email protected] http://mailman.qos.ch/mailman/listinfo/slf4j-dev
