Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.java.programmer > #39870
| From | Andreas Leitgeb <avl@logic.at> |
|---|---|
| Newsgroups | comp.lang.java.programmer |
| Subject | Re: slf4j update |
| Date | 2022-12-13 10:27 +0000 |
| Organization | A noiseless patient Spider |
| Message-ID | <slrntpgkt8.21q.avl@logic.at> (permalink) |
| References | <082e7784-803e-47a8-a224-52447f2592afn@googlegroups.com> |
e.d.pro...@gmail.com <e.d.programmer@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)
Back to comp.lang.java.programmer | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
slf4j update "e.d.pro...@gmail.com" <e.d.programmer@gmail.com> - 2022-12-12 14:37 -0800
Re: slf4j update Andreas Leitgeb <avl@logic.at> - 2022-12-13 10:27 +0000
Re: slf4j update "e.d.pro...@gmail.com" <e.d.programmer@gmail.com> - 2022-12-13 04:06 -0800
csiph-web