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/04/19 16:54:25 UTC

[jira] [Created] (TINKERPOP-1268) Improve script execution options for console

stephen mallette created TINKERPOP-1268:
-------------------------------------------

             Summary: Improve script execution options for console
                 Key: TINKERPOP-1268
                 URL: https://issues.apache.org/jira/browse/TINKERPOP-1268
             Project: TinkerPop
          Issue Type: Improvement
          Components: console
    Affects Versions: 3.1.2-incubating
            Reporter: stephen mallette
            Assignee: stephen mallette
             Fix For: 3.1.3


Given the discussion here:


Implement the following:

1. Deprecate support for {{ScriptExecutor}}
2. Deprecate support of bin/gremlin.sh init.groovy
3. Add support for {{bin/gremlin.sh -i init.groovy}} which does the same thing as (2) and does not exit the console on failure. That would allow a user to work with their console session up to the point of failure.
4. Improve support for {{bin/gremlin.sh -e exec.groovy}} to no longer use {{ScriptExecutor}} and execute scripts directly in the console for automation purposes. 
5. Add some other options to control output to the console so that you could do {{bin/gremlin.sh -q -e exec.groovy}} which would execute in a quiet mode with no output, for example.

The idea would be to try to implement this without breaking change.



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