You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Chetan Mehrotra (JIRA)" <ji...@apache.org> on 2013/06/12 13:42:19 UTC

[jira] [Updated] (FELIX-4122) Felix Script Console Plugin

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

Chetan Mehrotra updated FELIX-4122:
-----------------------------------

    Attachment: org.apache.felix.webconsole.plugins.scriptconsole-0.0.1-SNAPSHOT-src.zip

Source file for the bundle

md5sum output
16fb06d93147331aaad5b5ea41aa02d3  org.apache.felix.webconsole.plugins.scriptconsole-0.0.1-SNAPSHOT-src.zip
                
> Felix Script Console Plugin
> ---------------------------
>
>                 Key: FELIX-4122
>                 URL: https://issues.apache.org/jira/browse/FELIX-4122
>             Project: Felix
>          Issue Type: Improvement
>            Reporter: Chetan Mehrotra
>         Attachments: org.apache.felix.webconsole.plugins.scriptconsole-0.0.1-SNAPSHOT-src.zip
>
>
> I have implemented a Felix WebConsole plugin for evaluating scripts. It greatly simplifies debugging issues related to OSGi by allowing admin to inspect runtime state via scripts. It is a port of Sling Script Console Plugin (SLING-2463) but it has no other dependency.  It provides support for following items
> * Support evaluation of script in any language  e.g. Groovy, JavaScript, Ruby, Python etc. You would need to ensure that relevant language bundle is deployed
> * Code editor with syntax highlighting support based on CodeMirror Javascript library
> * Hot key support
> * Execute remote testcase via evaluating test scripts
> The code is pushed to my forked Git repo for Felix at [1]. Complete details about the plugin (with screen shots) is provided at [2]. The wiki refer to 
> Comments and feedback welcome!!
> [1] https://github.com/chetanmeh/felix-script-console
> [2] https://github.com/chetanmeh/c/wiki/Felix-Script-Console

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira