Skip to content

Conversation

@kwin
Copy link
Member

@kwin kwin commented Jan 29, 2026

This provides a SLF4J implementation for JEP 264 Loggers This closes #11684

Following this checklist to help us incorporate your
contribution quickly and easily:

  • Your pull request should address just one issue, without pulling in other changes.
  • Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
  • Each commit in the pull request should have a meaningful subject line and body.
    Note that commits might be squashed by a maintainer on merge.
  • Write unit tests that match behavioral changes, where the tests fail if the changes to the runtime are not applied.
    This may not always be possible but is a best-practice.
  • Run mvn verify to make sure basic checks pass.
    A more thorough check will be performed on your pull request automatically.
  • You have run the Core IT successfully.

If your pull request is about ~20 lines of code you don't need to sign an
Individual Contributor License Agreement if you are unsure
please ask on the developers list.

To make clear that you license your contribution under
the Apache License Version 2.0, January 2004
you have to acknowledge this by using the following check-box.

This provides a SLF4J implementation for JEP 264 Loggers
This closes #11684
@kwin kwin requested review from cstamas and desruisseaux January 29, 2026 11:25
@kwin kwin marked this pull request as ready for review January 29, 2026 11:57
Copy link
Contributor

@desruisseaux desruisseaux left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm neutral on this one. My preference would be to go the opposite way (drop SLF4J, use platform logging or java.util.logging instead), but I realize that it may be too much work for now.

@cstamas
Copy link
Member

cstamas commented Jan 29, 2026

Since Maven 3.1 the "go to API" was slf4j (while Plexus logger still existed and exists from Maven2 times). I agree that by cutting off legacy we could really shrink the classpath, but at the same time it would introduce huge compatibility issue.

@gnodet
Copy link
Contributor

gnodet commented Jan 29, 2026

The idea of bridging various APIs to a single backend is fine. I think this PR goes into the right direction. Whether we want to change the backend, or the official API is a different story.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Provide Platform Logging Service (System.LoggerFinder) in Maven

4 participants