You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Clebert Suconic (Jira)" <ji...@apache.org> on 2020/04/23 17:24:00 UTC
[jira] [Issue Comment Deleted] (ARTEMIS-2734) Implement Apache
logger for the testsuite
[ https://issues.apache.org/jira/browse/ARTEMIS-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Clebert Suconic updated ARTEMIS-2734:
-------------------------------------
Comment: was deleted
(was: This is not an issue in production, but it is an issue on the testsuite.
In production, we set the logger on the bootstrap class loader what would set things right.
However on the testsuite classes that are using Apache Logging (e.g. BeanUtils) are throwing everything under debug mode, which goes to the System.out.
We should implement a Bridge logger for the testsuite so things are filtered appropriately.)
> Implement Apache logger for the testsuite
> -----------------------------------------
>
> Key: ARTEMIS-2734
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2734
> Project: ActiveMQ Artemis
> Issue Type: Test
> Components: Tests
> Reporter: Clebert Suconic
> Priority: Major
> Fix For: 2.13.0
>
>
> This is not an issue in production, but it is an issue on the testsuite.
>
> In production, we set the logger on the bootstrap class loader what would set things right.
>
> However on the testsuite classes that are using Apache Logging (e.g. BeanUtils) are throwing everything under debug mode, which goes to the System.out.
>
> We should implement a Bridge logger for the testsuite so things are filtered appropriately.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)