| Index | index by Group | index by Distribution | index by Vendor | index by creation date | index by Name | Mirrors | Help | Search |
| Name: slf4j-jdk14 | Distribution: openSUSE Tumbleweed |
| Version: 2.0.18 | Vendor: openSUSE |
| Release: 1.2 | Build date: Mon Jul 13 13:32:42 2026 |
| Group: Development/Libraries/Java | Build host: reproducible |
| Size: 10258 | Source RPM: slf4j-2.0.18-1.2.src.rpm |
| Packager: https://bugs.opensuse.org | |
| Url: https://www.slf4j.org/ | |
| Summary: SLF4J JDK14 Binding | |
SLF4J JDK14 Binding.
Apache-2.0 AND MIT
* Mon Jul 13 2026 Fridrich Strba <fstrba@suse.com>
- Upgrade to 2.0.18
* Breaking Changes & Compatibility
+ Minimum Java Requirement Bump: The baseline Java requirement
has been upgraded from Java 5 (in the 1.7.x series) to Java 8.
+ New Backend Discovery Mechanism: SLF4J no longer relies on the
legacy StaticLoggerBinder class-path search mechanism. It has
fully migrated to using the Java ServiceLoader mechanism (SPI)
to discover logging backends. Downstream logging providers
(like Logback or SLF4J bridges) must be updated to versions
that support ServiceLoader to function with SLF4J 2.x.
+ Explicit Provider Override: Introduced the slf4j.provider
system property, allowing administrators or developers to
explicitly specify the logging provider class, bypassing the
ServiceLoader mechanism entirely for faster initialization.
* New Features & Enhancements
+ Fluent Logging API: Introduced a backward-compatible fluent
logging API (e.g., logger.atInfo().setMessage("...").log()).
Existing clients using the traditional logging methods do not
need to rewrite their code.
+ JPMS Modularity: SLF4J has been fully modularized in
accordance with the Java Platform Module System (JPMS)
specifications.
+ BOM Artifact: Introduced a Bill of Materials (BOM) file
(added in 2.0.8) to help downstream projects easily
synchronize and align versions across all org.slf4j bridge and
API packages.
* Notable Internal Fixes
+ MDC Initialization Race Condition: Fixed an edge-case bug
where the Mapped Diagnostic Context (MDC) could be initialized
before the LoggerFactory, which occasionally resulted in the
MDC getting stuck using an incorrect MDCAdapter instance.
- Generate the ant build system from the upstream maven build and
adapt it
- Removed patches:
* build-remove-slf4j_api-binder.patch
* slf4j-commons-lang3.patch
* slf4j-reload4j-bundlename.patch
+ not needed with this version
* Tue Jul 22 2025 Fridrich Strba <fstrba@suse.com>
- Remove stale pre_checkin.sh file
* Tue Sep 24 2024 Fridrich Strba <fstrba@suse.com>
- Use SOURCE_DATE_EPOCH for reproducible jar mtime
* Tue Feb 20 2024 Fridrich Strba <fstrba@suse.com>
- Use %patch -P N instead of deprecated %patchN.
* Tue May 30 2023 Fridrich Strba <fstrba@suse.com>
- Do not require junit and ant-junit, since we don't run tests
during the build
* Wed Jul 06 2022 Fridrich Strba <fstrba@suse.com>
- Add symlink to reload4j -> log4j12 for applications that expect
that name.
* Sat Mar 19 2022 Fridrich Strba <fstrba@suse.com>
- Build with source/target levels 8
* Fri Feb 25 2022 Fridrich Strba <fstrba@suse.com>
- Upgrade to 1.7.36
* Changes in 1.7.36:
+ Correct corrupt "Export-Package" declaration in MANIFEST.MF
in log4j-over-slf4j module
+ Starting with version 1.7.36, slf4j releases will be
reproducible. By reproducible we mean that anyone checking out
the code corresponding to the release version from source code
repository and building that local copy, will obtain an
identical binary to the published binary.
* Changes 1.7.35
+ In this release, the "slf4j-log4j12" artifact automatically
instructs Maven to use the "slf4j-reload4j" artifact instead.
As you might have guessed, the "slf4j-reload4j" binding
delegates log processing to the reload4j logging framework.
+ Fix incorrect version number in the relocation element in
slf4j-log4j12/pom.ml
* Changes in 1.7.34
+ The relocation element in slf4j-log4j12 had incorrect version
number. Version 1.7.34 should not be used.
* Changes in 1.7.33
+ SLF4J now ships with the slf4j-reload4j module delegating to
the reload4j backend.
+ SimpleLogger now prints the thread Id if instructed to do so.
This fixes SLF4J-499.
- Added patch:
* slf4j-reload4j-bundlename.patch
+ fix a typo in source reload4k -> reload4j
* Thu Feb 24 2022 Fridrich Strba <fstrba@suse.com>
- Do not use a separate spec file for sources, since now they
can be built in the same run as the other artifacts
* Wed Feb 23 2022 Fridrich Strba <fstrba@suse.com>
- Removed patch:
* slf4j-reload4j.patch
+ the incompatibility is now handled in reload4j itself
/usr/share/java/slf4j /usr/share/java/slf4j/jdk14.jar /usr/share/java/slf4j/slf4j-jdk14.jar /usr/share/maven-metadata/slf4j-jdk14.xml /usr/share/maven-poms/slf4j /usr/share/maven-poms/slf4j/jdk14.pom
Generated by rpm2html 1.8.1
Fabrice Bellet, Sun Aug 2 01:28:36 2026