[
https://issues.apache.org/jira/browse/ROCKETMQ-178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15970635#comment-15970635
]
ASF GitHub Bot commented on ROCKETMQ-178:
-----------------------------------------
Github user coveralls commented on the issue:
https://github.com/apache/incubator-rocketmq/pull/93
[](https://coveralls.io/builds/11106432)
Coverage decreased (-0.03%) to 34.591% when pulling
**08e0fd18460510cdb6500067addfaf21dbe7a1c8 on lizhanhui:ROCKETMQ-178** into
**7bcb3b3eae1e3c441861f2a3cd79ff54a8e691b9 on apache:develop**.
> Broker -m -p options are broken
> -------------------------------
>
> Key: ROCKETMQ-178
> URL: https://issues.apache.org/jira/browse/ROCKETMQ-178
> Project: Apache RocketMQ
> Issue Type: Bug
> Components: rocketmq-broker
> Affects Versions: 4.1.0-incubating
> Reporter: Zhanhui Li
> Assignee: Zhanhui Li
> Fix For: 4.1.0-incubating
>
>
> Broker command line are supposed to support -m -p options to print out
> important settings. Now the logger is set as null, thus, no output at all.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)