Path: csiph.com!weretis.net!feeder8.news.weretis.net!eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail From: Andreas Leitgeb Newsgroups: comp.lang.java.programmer Subject: Re: slf4j update Date: Tue, 13 Dec 2022 10:27:52 -0000 (UTC) Organization: A noiseless patient Spider Lines: 13 Message-ID: References: <082e7784-803e-47a8-a224-52447f2592afn@googlegroups.com> Reply-To: avl@logic.at Injection-Date: Tue, 13 Dec 2022 10:27:52 -0000 (UTC) Injection-Info: reader01.eternal-september.org; posting-host="5767d4c8ca9ebb63a73868e9902c85cf"; logging-data="2624950"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+NjPRMO/Gsc6tQ+o0ux0yc" User-Agent: slrn/1.0.3 (Linux) Cancel-Lock: sha1:DcDbgHSWv7UrWfcWtCgTEwlKfek= Xref: csiph.com comp.lang.java.programmer:39870 e.d.pro...@gmail.com wrote: > Usually if you update a maven dependency version, you just change the number and fix any code that gets errors. > Today I learned there's a new version of slf4j, if you update it doesn't give any errors, it just doesn't work. You have to change a corresponding dependency, on artifact name not just version number. > https://mvnrepository.com/artifact/org.apache.logging.log4j/log4j-slf4j2-impl Thanks for the heads-up, but please elaborate a bit more... - what is the visible symptom of "it just doesn't work" ? (so others could recognize the symptoms) - which previous artifact name needs to be changed to the given one? (so others could scan their deps for the old name)