Bump SLF4J API to version 2.0.2

[joschi]

SLF4J 2.0.0, 2.0.1, and 2.0.2 have been released recently.

https://www.slf4j.org/news.html

2022-09-20 - Release of SLF4J 2.0.2

• Fixed bug in the setContextMap() method of Reload4jMDCAdapter. This issue was reported in SLF4J-563 by Michael Wartes.
• The binary of this version can be reproduced by checking out the tag v_2.0.2 from the source code repository (GitHub). Release built using Java "18" 2022-03-22 build 18+36-2087 under Linux Debian 11.2.

2022-09-14 - Release of SLF4J 2.0.1

• The Logger.makeLoggingEventBuilder method semantics has changed so that overriding implementations should now always build a new LoggingEventBuilder instance as appropraiate for the implementation, i.e the logging backend. For more details see SLF4J-560.
• Deprecated unused LoggerFactoryBinder and MarkerFactoryBinder classes. This issue was raised in SLF4J-555 by Witalij Berdinskich who provided the relevant patch.
• The binary of this version can be reproduced by checking out the tag v_2.0.1 from the source code repository (GitHub). Release built using Java "18" 2022-03-22 build 18+36-2087 under Linux Debian 11.2.

2022-08-20 - Release of SLF4J 2.0.0

The the 2.0.x series requires Java 8 and adds a backward-compatible fluent logging api.

Moreover, SLF4J has been modularized per JPMS/Jigsaw specification. The resulting internal changes are detailed in the FAQ page.
SLF4J 2.0.x series requires Java 8. It builds upon the 1.8.x series and adds a backward-compatible fluent logging api. By backward-compatible, we mean that existing logging frameworks do not have to be changed for the user to benefit from the fluent logging API. However, existing frameworks must migrate to the ServiceLoader mechanism. The resulting internal changes are detailed in the FAQ page.

• Except minor javadoc changes, this release is identical to 2.0.0-beta1 released earlier this month.
• The binary of this version can be reproduced by checking out the tag v_2.0.0 from the source code repository (GitHub). Release built using Java "18" 2022-03-22 build 18+36-2087 under Linux Debian 11.2.

[joschi]

Related PR for Jetty: jetty/jetty.project#8603

[senivam]

In order to avoid dependency convergence error, it's either required to wait until Jetty releases the 11.0.13 and bump slf4j along with Jetty versions or temporarily exclude slf4j from the actual Jetty and merge the PR with those exclusions.

[senivam]

now there are some issues with CI job's connection to the Eclipse's Maven:

 transfer failed for https://repo.eclipse.org/content/repositories/maven_central/org/apache/httpcomponents/core5/httpcore5-h2/5.1.2/httpcore5-h2-5.1.2.jar, status: 502 Bad Gateway

so, the build might be performed later, when the issue is resolved.

[joschi]

@senivam Since the PRs in the Jetty project have been merged, I think waiting for a new release could make more sense over excluding the SLF4J dependencies of Jetty in Jersey.

[senivam]

@joschi sure, so this PR will be delayed until a new version of Jetty is in central.

[jansupol]

Superseded by #5185.