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

ASF GitHub Bot commented on S2GRAPH-227:
----------------------------------------

GitHub user SteamShon opened a pull request:

    https://github.com/apache/incubator-s2graph/pull/177

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

    - version up slf4j bindings.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/SteamShon/incubator-s2graph S2GRAPH-227

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-s2graph/pull/177.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #177
    
----
commit 187b2b55152a7515617d42a599897a8f6ef6a11c
Author: DO YUNG YOON <steamshon@...>
Date:   2018-06-21T06:15:09Z

    version up slf4j bindings.

----


> 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)

Reply via email to