[
https://issues.apache.org/jira/browse/AMQ-8484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17490901#comment-17490901
]
Robbie Gemmell edited comment on AMQ-8484 at 2/11/22, 1:26 PM:
---------------------------------------------------------------
Feels like reload4j reloaded changes should go on the original AMQ-8472 JIRA
given it hasnt been released.
Note that activemq-partition 5.16.3 was actually already passing log4j (1.2.16)
on to dependents since it is a compile scope dependency of the 'linkedin
zookeeper' stuff that it depends on. So it passing on reload4j instead of log4j
is actually consistent with that. Obviously anyone who was excluding log4j will
then get reload4j in the new case where they didnt get log4j, but thats to be
expected as the dependencies did change.
was (Author: gemmellr):
Feels like reload4j reloaded changes should go on the original AMQ-8472 JIRA
given it hasnt been released.
Note that activemq-partition 5.16.3 was actually already passing log4j (1.2.16)
on to depenedents since it is a compile scope dependency of the zookeeper that
it depends on. So it passing on reload4j instead of log4j is actually
consistent with that. Obviously anyone who was excluding log4j will then get
reload4j in the new case where they didnt get log4j, but thats to be expected
as the dependencies did change.
> reload4j scope is not correct
> -----------------------------
>
> Key: AMQ-8484
> URL: https://issues.apache.org/jira/browse/AMQ-8484
> Project: ActiveMQ
> Issue Type: Bug
> Reporter: Jean-Baptiste Onofré
> Assignee: Jean-Baptiste Onofré
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> reload4j scope should be test in several modules, for instance like
> activemq-partition.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
