[
https://issues.apache.org/jira/browse/LOG4J2-3118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17376532#comment-17376532
]
Carter Kozak commented on LOG4J2-3118:
--------------------------------------
I believe the quarkus fork is subtly different in order to support graalvm
native-image with build-time class initialization. It can be difficult to get
log4j wired up in a native application, but if you're running hotspot it will
be fine.
> Quarkus / Jboss Logging
> -----------------------
>
> Key: LOG4J2-3118
> URL: https://issues.apache.org/jira/browse/LOG4J2-3118
> Project: Log4j 2
> Issue Type: Question
> Components: Core
> Affects Versions: 2.14.1
> Reporter: Paul Rubin
> Priority: Minor
>
> We want to use the configurability and flexibility of Log4j2 in quarkus
> services. These services are from a Jboss / Wildfly basis and use Jboss
> logging.
>
> While they claim that the jboss backend is preferred that this logging will
> use log4j2 as the backend of the jboss backjend is missing.
> Can anyone tell me what specifically I need to remove to make this work?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
