[jira] [Resolved] (ARTEMIS-3126) please do not force jboss-logmanager on users

["Justin Bertram (Jira)" <ji...@apache.org>]

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

Justin Bertram resolved ARTEMIS-3126.
-------------------------------------
    Resolution: Duplicate

> please do not force jboss-logmanager on users
> ---------------------------------------------
>
>                 Key: ARTEMIS-3126
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-3126
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>    Affects Versions: 2.14.0
>            Reporter: Stuart Halloway
>            Priority: Minor
>
> I have maintained a codebase using ActiveMQ since the HornetQ days. It has been terrific for both stability and performance.
> Every once in a while I have to upgrade dependencies, mostly due to security advisories. On the latest upgrade, I found that ActiveMQ now "sort of" compels users to choose JBoss logging. In particular, the server dependency on jboss-logmanager causes users of any other logging library to encounter this [JBoss error.|https://github.com/jboss-logging/jboss-logmanager/blob/master/core/src/main/java9/org/jboss/logmanager/JBossLoggerFinder.java#L68-L74] This error is difficult to avoid, since it will happen the first time code in any library tries to get a j.u.logger. 
> I do not want or need jboss logging, and I cannot force it on my users. ActiveMQ doesn't seem to really need it either - if I maven exclude jboss-logmanager from ActiveMQ my test suite passes, logging via slf4j. This strongly suggests that jboss-logmanager is needed only in some contexts.
> Thanks for ActiveMQ!  
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)