You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@edgent.apache.org by "Dale LaBossiere (JIRA)" <ji...@apache.org> on 2016/12/09 14:30:59 UTC
[jira] [Commented] (EDGENT-317) Slf4j error
[ https://issues.apache.org/jira/browse/EDGENT-317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15735458#comment-15735458 ]
Dale LaBossiere commented on EDGENT-317:
----------------------------------------
Ultimately an slf4j implementation (not just api) must be on the classpath. This is noted in the "overview" in the javadoc... hmm, I see that doc says slf4j-jdk-1.7.12.jar whereas its really slf4j-jdk14-1.7.12.jar that's in ext (notice "jdk" vs "jdk14"). Maybe that doc has mislead you?
Fwiw, the Edgent build creates edgent.samples.topology.jar for that sample and its manifest includes a path to the slf4j-jdk14-1.7.12.jar that's included in the java8/ext directory. So when you run ./runhelloedgent.sh when in build/distributions/java8/scripts (or the same from a built binary bundle) it should just work.
Does that clear things up?
> Slf4j error
> -----------
>
> Key: EDGENT-317
> URL: https://issues.apache.org/jira/browse/EDGENT-317
> Project: Edgent
> Issue Type: Bug
> Components: Samples
> Affects Versions: Apache Edgent 1.0.0
> Environment: Apache Edgent programming
> Reporter: suhasjk
> Priority: Blocker
> Fix For: Apache Edgent 1.0.0
>
>
> Hello Team,
> While running a sample "Hello Edgent" program, we are getting the following error in eclipse:
> I tried setting classpath, even imported the required slf4j jar files, but no use.
> slf4j: failed to load class org.slf4j.impl.staticloggerbinder
> slf4j: defaulting to no-operation (nop) logger implementation
> slf4j see http //www.slf4j.org/codes.html#staticloggerbinder for further details
> Hello
> Edgent!
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)