Upgrade SLF4J to version 1.7.35

[oscerd]

2022-01-13 - Release of SLF4J 1.7.33

• SLF4J now ships with the slf4j-reload4j module delegating to the reload4j backend. Reload4j is a drop-in replacement for log4j version 1.2.17.

• SimpleLogger now prints the thread Id if instructed to do so. This fixes SLF4J-499 requested by Michael Osipov

[gnodet]

2022-01-13 - Release of SLF4J 1.7.33

• SLF4J now ships with the slf4j-reload4j module delegating to the reload4j backend. Reload4j is a drop-in replacement for log4j version 1.2.17.

• SimpleLogger now prints the thread Id if instructed to do so. This fixes SLF4J-499 requested by Michael Osipov

FTR, I don't think mvnd is impacted by those two issues as the backend used is logback.

[ppalaga]

2022-01-13 - Release of SLF4J 1.7.33
• SLF4J now ships with the slf4j-reload4j module delegating to the reload4j backend. Reload4j is a drop-in replacement for log4j version 1.2.17.
• SimpleLogger now prints the thread Id if instructed to do so. This fixes SLF4J-499 requested by Michael Osipov

FTR, I don't think mvnd is impacted by those two issues as the backend used is logback.

Yes, we have not used log4j 1.x, but we do use slf4j-simple in the client.

Thanks the PR @oscerd

[gnodet]

FTR, I don't think mvnd is impacted by those two issues as the backend used is logback.

Yes, we have not used log4j 1.x, but we do use slf4j-simple in the client.

Right, I forgot about that. That makes we wonder if the following file is used at all:
https://github.com/apache/maven-mvnd/blob/79137867e51e04e24ae1e924afbd2e4f77e2d860/dist/src/main/distro/conf/logback-client.xml

[ppalaga]

makes we wonder if the following file is used at all:
https://github.com/apache/maven-mvnd/blob/79137867e51e04e24ae1e924afbd2e4f77e2d860/dist/src/main/distro/conf/logback-client.xml

Yes, it is probably a left-over from earlier times when we used or wanted to use logback on the client.