[
https://issues.apache.org/jira/browse/LOG4J2-3282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17464874#comment-17464874
]
Ralph Goers commented on LOG4J2-3282:
-------------------------------------
The guidance is basically that the artifactId and package name must be unique
and must describe what the module does. So tojul would make sense as a package
name and log4j-to-jul would make sense as an artifactId and module name.
All that said, I believe you are the first person to request this since Log4j 2
was started. I believe the primary reason we have never done this is that we
really don't want to encourage people to use java.util.logging. That said it
would improve greatly by one simple change - to use ServiceLoader to locate the
LogManager implementation.
> 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
> Priority: Major
> Fix For: 2.17.1
>
>
> 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)
