Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.java.programmer > #39869 > unrolled thread
| Started by | "e.d.pro...@gmail.com" <e.d.programmer@gmail.com> |
|---|---|
| First post | 2022-12-12 14:37 -0800 |
| Last post | 2022-12-13 04:06 -0800 |
| Articles | 3 — 2 participants |
Back to article view | Back to comp.lang.java.programmer
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
| From | "e.d.pro...@gmail.com" <e.d.programmer@gmail.com> |
|---|---|
| Date | 2022-12-12 14:37 -0800 |
| Subject | slf4j update |
| Message-ID | <082e7784-803e-47a8-a224-52447f2592afn@googlegroups.com> |
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
[toc] | [next] | [standalone]
| From | Andreas Leitgeb <avl@logic.at> |
|---|---|
| Date | 2022-12-13 10:27 +0000 |
| Message-ID | <slrntpgkt8.21q.avl@logic.at> |
| In reply to | #39869 |
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)
[toc] | [prev] | [next] | [standalone]
| From | "e.d.pro...@gmail.com" <e.d.programmer@gmail.com> |
|---|---|
| Date | 2022-12-13 04:06 -0800 |
| Message-ID | <198075d9-f192-419b-9bbc-a39373736122n@googlegroups.com> |
| In reply to | #39870 |
On Tuesday, December 13, 2022 at 5:28:08 AM UTC-5, Andreas Leitgeb wrote: > - what is the visible symptom of "it just doesn't work" ? > (so others could recognize the symptoms) > Using slf4j-api 2.0.2 or newer with log4j-slf4j-impl was printing stuff to eclipse console, nothing wrote to the log files. It doesn't make the connection, fails silently. > - which previous artifact name needs to be changed to the given one? > (so others could scan their deps for the old name) The old slf4j-api 1.x goes with a log4j-slf4j-impl. The new slf4j-api has to have log4j-slf4j2-impl.
[toc] | [prev] | [standalone]
Back to top | Article view | comp.lang.java.programmer
csiph-web