You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@s2graph.apache.org by "DOYUNG YOON (JIRA)" <ji...@apache.org> on 2018/06/21 06:18:00 UTC

[jira] [Updated] (S2GRAPH-227) version up SLF4J bindings(slf4j-log4j12) from 1.7.21 to 1.8.0-beta2

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

DOYUNG YOON updated S2GRAPH-227:
--------------------------------
    Summary: version up SLF4J bindings(slf4j-log4j12) from 1.7.21 to 1.8.0-beta2  (was: version up slf4j-log4j12 from 1.7.21 to 1.8.0-beta2)

> version up SLF4J bindings(slf4j-log4j12) from 1.7.21 to 1.8.0-beta2
> -------------------------------------------------------------------
>
>                 Key: S2GRAPH-227
>                 URL: https://issues.apache.org/jira/browse/S2GRAPH-227
>             Project: S2Graph
>          Issue Type: Bug
>          Components: s2graphql
>            Reporter: DOYUNG YOON
>            Assignee: DOYUNG YOON
>            Priority: Trivial
>
> In the development environment, the log messages are not redirected to stdout, which make development hard. 
> I found out upgrade version of slf4j-log4j12, jcl-over-slf4j, jul-to-slf4j from 1.7.21 to 1.8.0-beta2 fixed this issue on my setup. 



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