[
https://issues.apache.org/jira/browse/S2GRAPH-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15727131#comment-15727131
]
Jong Wook Kim commented on S2GRAPH-138:
---------------------------------------
Thanks for the report, this was indeed caused by S2GRAPH-117.
In the subproject s2rest_play, {{log4j}} and {{slf4j-log4j12}} were not being
included in {{managedClasspath}} due to some complication in the SBT settings.
I have updated the settings to properly include the dependencies.
Furthermore, we needed log4j.properties which configures the logging output.
For that, I have specified that the {{resourceDirectory}} should be added to
{{unmanagedClasspath}} in runtime, and created a symlink at
{{./s2rest_play/conf/log4j.properties}} pointing {{./conf/log4j.properties}}.
> There is a problem that `log` is not left in development mode.
> --------------------------------------------------------------
>
> Key: S2GRAPH-138
> URL: https://issues.apache.org/jira/browse/S2GRAPH-138
> Project: S2Graph
> Issue Type: Bug
> Reporter: Daewon Jeong
> Priority: Minor
>
> Logging works fine in packaged binary(sbt package) with `start-s2graph.sh`
> command.
> In development mode `sbt 'project s2rest_play' run`, logging does not work
> with the following message.
> {code}
> SLF4J: Failed to load class "org.slf4j.impl.StaticMDCBinder".
> SLF4J: Defaulting to no-operation MDCAdapter implementation.
> SLF4J: See http://www.slf4j.org/codes.html#no_static_mdc_binder for further
> details.
> {code}
> p.s: I think it seems to be related to {{S2GRAPH-117}} issue
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
