[ 
https://issues.apache.org/jira/browse/SCB-752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16546615#comment-16546615
 ] 

ASF GitHub Bot commented on SCB-752:
------------------------------------

coveralls commented on issue #813: [SCB-752] provide a configuration to 
determine whether to output merged.log4j.properties
URL: 
https://github.com/apache/incubator-servicecomb-java-chassis/pull/813#issuecomment-405583070
 
 
   
   [![Coverage 
Status](https://coveralls.io/builds/18023564/badge)](https://coveralls.io/builds/18023564)
   
   Coverage increased (+0.02%) to 87.081% when pulling 
**2592afc6ee82134d5d66e76a9120500bf0564f16 on 
yhs0092:user_can_switch_off_merged_log4j_properties_file** into 
**6c4c1c1e9adc8e99fcc57cc4165576dc9655c4d9 on apache:master**.
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


> User can switch off outputting merged log4j property file
> ---------------------------------------------------------
>
>                 Key: SCB-752
>                 URL: https://issues.apache.org/jira/browse/SCB-752
>             Project: Apache ServiceComb
>          Issue Type: New Feature
>          Components: Java-Chassis
>            Reporter: YaoHaishi
>            Assignee: YaoHaishi
>            Priority: Minor
>             Fix For: java-chassis-1.1.0
>
>
> On service start up, ServiceComb-java-chassis will try to output a merged 
> log4j property file onto hard disk and users cannot switch off this function.
> Maybe we can provide a configuration to let users decide whether this 
> function should work.
> Configuration key is 
> {code:java}
> log4j.logger.outputConfig.enabled
> {code}
> this is configured in log4j.properties file and the value is true or false.
> Default value is true.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to