You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Chetan Mehrotra (JIRA)" <ji...@apache.org> on 2014/05/28 12:58:02 UTC

[jira] [Resolved] (OAK-1845) Add command to execute script

     [ https://issues.apache.org/jira/browse/OAK-1845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chetan Mehrotra resolved OAK-1845.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 1.1

The requirements are now addressed via groovy based shell support. So explicit eval command not required unless we need to support evaluating scripts in lang other than Groovy. If such a need arises specific issue can be created 

> Add command to execute script
> -----------------------------
>
>                 Key: OAK-1845
>                 URL: https://issues.apache.org/jira/browse/OAK-1845
>             Project: Jackrabbit Oak
>          Issue Type: Sub-task
>          Components: run
>            Reporter: Chetan Mehrotra
>            Assignee: Chetan Mehrotra
>             Fix For: 1.1
>
>
> Add a command which can execute arbitrary script
> {noformat}
> > script /path/to/script
> > script -groovy println 'Hello'
> > script print("hello")
> > script <<EOT
> println(nodeStore.getRoot())
> EOT
> {noformat}
> For the last the script would be assumed to be javascript by default. Later we can enhance the Console to read multi line string use herestring 
> The ConsoleSession can be exposed as bind variable and can be used by script to access the runtime



--
This message was sent by Atlassian JIRA
(v6.2#6252)