[
https://issues.apache.org/jira/browse/AMQ-7426?focusedWorklogId=730959&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-730959
]
ASF GitHub Bot logged work on AMQ-7426:
---------------------------------------
Author: ASF GitHub Bot
Created on: 22/Feb/22 14:27
Start Date: 22/Feb/22 14:27
Worklog Time Spent: 10m
Work Description: gemmellr commented on pull request #662:
URL: https://github.com/apache/activemq/pull/662#issuecomment-1047851751
I would say so, if the idea is to not use Log4J 1.x, then there should be no
trace of it. Those bits should be using Log4J 2 (via the 1.2 bridge), or a less
apealling alternative would be subbing in reload4j, but that doesnt really make
sense given the context.
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 730959)
Time Spent: 5h 40m (was: 5.5h)
> Upgrade to log4j2
> -----------------
>
> Key: AMQ-7426
> URL: https://issues.apache.org/jira/browse/AMQ-7426
> Project: ActiveMQ
> Issue Type: Task
> Components: Broker
> Reporter: Jean-Baptiste Onofré
> Assignee: Jean-Baptiste Onofré
> Priority: Major
> Fix For: 5.17.0
>
> Time Spent: 5h 40m
> Remaining Estimate: 0h
>
> This JIRA will upgrade 5.17.x to use Log4J 2.x instead of 1.x
> (5.16.x was switched to using [reload4j|https://reload4j.qos.ch/] instead of
> Log4j 1.x via AMQ-8472 in 5.16.4)
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
