[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:comment-tabpanel&focusedCommentId=13992112#comment-13992112 ] 

Boris Unckel commented on LOGMGR-265:
-------------------------------------

[~jamezp] Sorry for the late response. You're right, this issue belongs to the wrong log4j2 documentation,  not to your implementation. My mistake: I backported this to WF12 which is on JBoss Modules 1.7. There is need to declare a service import on the importing module side. With JBoss Modules 1.8 you declare the service provision on the exporting module side.

>  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)