You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@logging.apache.org by "Ralph Goers (JIRA)" <ji...@apache.org> on 2019/06/18 04:38:00 UTC

[jira] [Resolved] (LOG4J2-18) Better compatibility with JBoss

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

Ralph Goers resolved LOG4J2-18.
-------------------------------
    Resolution: Invalid

Closing this issue as no one has ever reported it as a problem.

> Better compatibility with JBoss
> -------------------------------
>
>                 Key: LOG4J2-18
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-18
>             Project: Log4j 2
>          Issue Type: Improvement
>         Environment: JBoss and perhaps other "containers"
>            Reporter: Ralph Goers
>            Assignee: Ralph Goers
>            Priority: Major
>
> JBoss currently uses log4j for its own logging purposes. This causes numerous problems for applications that also want to use log4j for logging. JBoss has some documented methods for addressing the problems but none of them are particularly attractive. The goals for this issue should be:
> 1. Allow each "application" to have its own configuration separate from JBoss' jboss-log4j.xml
> 2. Allow applications to provide their own log4j components (Appenders, layouts, filters, etc) without having to put them in JBoss' classpath or the server/lib directory.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)