[ARTEMIS-3126] please do not force jboss-logmanager on users

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Duplicate
• Affects Version/s: 2.14.0
• Assignee: Unassigned
• Reporter: Stuart Halloway
• Created: 18/Feb/21 21:06
• Updated: 18/Apr/24 14:51
• Resolved: 18/Apr/24 14:51

Description

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. 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!  

 

 

Issue Links

• duplicates: ARTEMIS-4020 switch to using SLF4J for logging API and use Log4j 2 for broker distribution