[jboss-jira] [JBoss JIRA] (LOGMGR-265) log4j2-jboss-logmanager: Service Provider wrong file

[Boris Unckel (Jira)]

     [ https://issues.redhat.com/browse/LOGMGR-265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Boris Unckel updated LOGMGR-265:
--------------------------------
    Description: 
Currently the service provider class is

https://github.com/jboss-logging/log4j2-jboss-logmanager/blob/master/src/main/resources/META-INF/services/org.apache.logging.log4j.spi.Provider

according to https://logging.apache.org/log4j/2.x/manual/extending.html it must be META-INF/services/org.apache.logging.spi.Provider (without the log4j in its name).

  was:
Currently the service provider class is

https://github.com/jboss-logging/log4j2-jboss-logmanager/blob/master/src/main/resources/META-INF/services/org.apache.logging_.log4j._spi.Provider

according to https://logging.apache.org/log4j/2.x/manual/extending.html it must be META-INF/services/org.apache.logging.spi.Provider (without the log4j in its name).



>  log4j2-jboss-logmanager: Service Provider wrong file
> -----------------------------------------------------
>
>                 Key: LOGMGR-265
>                 URL: https://issues.redhat.com/browse/LOGMGR-265
>             Project: JBoss Log Manager
>          Issue Type: Bug
>            Reporter: Boris Unckel
>            Priority: Blocker
>
> Currently the service provider class is
> https://github.com/jboss-logging/log4j2-jboss-logmanager/blob/master/src/main/resources/META-INF/services/org.apache.logging.log4j.spi.Provider
> according to https://logging.apache.org/log4j/2.x/manual/extending.html it must be META-INF/services/org.apache.logging.spi.Provider (without the log4j in its name).



--
This message was sent by Atlassian Jira
(v7.13.8#713008)