You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "stephen mallette (JIRA)" <ji...@apache.org> on 2016/02/17 16:57:18 UTC

[jira] [Commented] (TINKERPOP-1158) gremlin.sh -v emits log4j initialization errors

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

stephen mallette commented on TINKERPOP-1158:
---------------------------------------------

dah - {{gremlin.sh}} from the root stinks.  you should be able to run the {{bin/gremlin.sh}} in {{gremlin-console}} without trouble. i prefer to use the one in that is in the staged distribution itself {{gremlin-console/target/*stand*}} after {{mvn clean install}}.  

anyway, those options are both workarounds for the init problems we have with running it from root.   

> gremlin.sh -v emits log4j initialization errors
> -----------------------------------------------
>
>                 Key: TINKERPOP-1158
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-1158
>             Project: TinkerPop
>          Issue Type: Bug
>          Components: console
>    Affects Versions: 3.1.1-incubating
>            Reporter: Ariel Weisberg
>            Priority: Trivial
>
> I get a bunch of unrelated noise from log4j when I run hash [c0b79c5|https://github.com/apache/incubator-tinkerpop/tree/c0b79c5c65db6424407ca00144be5167052c6c6b].
> I am running from the bin directory of the repository after {{mvn clean install}}.
> {noformat}
> $ ./gremlin.sh -v
>  log4j:WARN No appenders could be found for logger (com.jcabi.manifests.Manifests).
> log4j:WARN Please initialize the log4j system properly.
> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
> gremlin 3.2.0-SNAPSHOT
> {noformat}



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