[jira] [Updated] (TINKERPOP-1019) Convert println in test to SLF4j

["stephen mallette (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/TINKERPOP-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stephen mallette updated TINKERPOP-1019:
----------------------------------------
    Description: 
Not sure why we used printlns for debugging.  We should just switch to slf4j and then control the output with the log4j.properties file.  We could then drop the special usage of the {{muteTestLogs}} system property.  

Part of this should be to sort out what's going on with controlling {{log4.properties}} from maven.  That creates problems apparently (attempted to do that on a different ticket and caused hadoop/spark stuff to fail)

  was:Not sure why we used printlns for debugging.  We should just switch to slf4j and then control the output with the log4j.properties file.  We could then drop the special usage of the {{muteTestLogs}} system property.  


> Convert println in test to SLF4j
> --------------------------------
>
>                 Key: TINKERPOP-1019
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-1019
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: test-suite
>    Affects Versions: 3.1.0-incubating
>            Reporter: stephen mallette
>            Assignee: stephen mallette
>            Priority: Minor
>             Fix For: 3.1.1-incubating
>
>
> Not sure why we used printlns for debugging.  We should just switch to slf4j and then control the output with the log4j.properties file.  We could then drop the special usage of the {{muteTestLogs}} system property.  
> Part of this should be to sort out what's going on with controlling {{log4.properties}} from maven.  That creates problems apparently (attempted to do that on a different ticket and caused hadoop/spark stuff to fail)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)