[
https://issues.apache.org/jira/browse/TINKERPOP-1158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15533366#comment-15533366
]
ASF GitHub Bot commented on TINKERPOP-1158:
-------------------------------------------
Github user dkuppitz commented on the issue:
https://github.com/apache/tinkerpop/pull/444
@okram We could get rid of the additional release steps if we would remove
the 2 extra `gremlin.sh` files. Any reason why you prefer those? If you're just
too lazy to type out the `target` path, you could create a bash alias. Look,
that's what I have in my `~/.bashrc`:
```
gremlin() {
args=$@
pushd
/projects/apache/tinkerpop/gremlin-console/target/*-gremlin-console-*-standalone
> /dev/null
if [ $? -eq 0 ]; then
bin/gremlin.sh ${args}
popd > /dev/null
else
echo "Gremlin Console binary does not exist."
fi
}
alias g=gremlin
```
And here's how it works:
```
daniel@cube ~ $ g -v
gremlin 3.1.5-SNAPSHOT
daniel@cube ~ $ g
\,,,/
(o o)
-----oOOo-(3)-oOOo-----
plugin activated: tinkerpop.server
plugin activated: tinkerpop.utilities
plugin activated: tinkerpop.tinkergraph
gremlin>
```
> 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
> Assignee: Daniel Kuppitz
> 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)