You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Carter Kozak (Jira)" <ji...@apache.org> on 2022/01/07 22:00:00 UTC

[jira] [Resolved] (LOG4J2-3282) log4j-to-jul JDK Logging Bridge

     [ https://issues.apache.org/jira/browse/LOG4J2-3282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carter Kozak resolved LOG4J2-3282.
----------------------------------
    Fix Version/s: 2.17.2
       Resolution: Fixed

> log4j-to-jul JDK Logging Bridge
> -------------------------------
>
>                 Key: LOG4J2-3282
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-3282
>             Project: Log4j 2
>          Issue Type: Improvement
>    Affects Versions: 2.17.0
>            Reporter: Michael Vorburger
>            Assignee: Michael Vorburger
>            Priority: Major
>             Fix For: 2.17.2
>
>
> I (we, internal project at work) would like to have a {{{}log4j-to-jul{}}}.
> So the "opposite" of [https://logging.apache.org/log4j/2.x/log4j-jul/] (from [https://github.com/apache/logging-log4j2/tree/master/log4j-jul]). The use case here is if one has an existing JUL-based set-up into which you would like to see logs from a library that has been coded against the Log4j API.
> Poking around [https://github.com/apache/logging-log4j2/tree/master/log4j-to-slf4j/src/main/java/org/apache/logging/slf4j], I hope this won't be very hard to do, unless I'm missing something. I want log4j-to-jul to only depend on log4j-api and nothing else, notably NOT log4j-core.
> Please assign this issue to me so that I can work on this and contribute it.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)