[
https://issues.apache.org/jira/browse/AMQ-8472?focusedWorklogId=725175&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-725175
]
ASF GitHub Bot logged work on AMQ-8472:
---------------------------------------
Author: ASF GitHub Bot
Created on: 11/Feb/22 14:40
Start Date: 11/Feb/22 14:40
Worklog Time Spent: 10m
Work Description: cshannon commented on pull request #766:
URL: https://github.com/apache/activemq/pull/766#issuecomment-1036278898
> Yes I was only talking about reload4j itself, in relation to log4j, that
it wasnt a change in behaviour to pass reload4j on as log4j was already being
passed on via the 'linkedin'/zookeeper bits before.
>
> As the new JIRA didnt mention it, I didnt realise the point actually
centred more around the slf4j bit. I'd agree that as the slf4j-log4j12
equivalent wasnt being passed on before the slf4j-reload4j equivalent shouldnt
be now.
Ok so maybe we just drop the slf4j part and keep reload4j and let people
exclude if they want.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: gitbox-unsubscr...@activemq.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 725175)
Time Spent: 6h 20m (was: 6h 10m)
> Switch to reload4j for logging
> ------------------------------
>
> Key: AMQ-8472
> URL: https://issues.apache.org/jira/browse/AMQ-8472
> Project: ActiveMQ
> Issue Type: Improvement
> Reporter: Colm O hEigeartaigh
> Assignee: Jean-Baptiste Onofré
> Priority: Major
> Fix For: 5.16.4
>
> Time Spent: 6h 20m
> Remaining Estimate: 0h
>
> This task is to switch AMQ 5.16.x to use Reload4J instead of Log4J for
> logging. That way we get fixes for the various CVEs in Log4J 1.x, until AMQ
> picks up Log4J 2.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
