Mailing-List: contact issues-help@karaf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@karaf.apache.org
Date: Fri, 26 Apr 2013 13:38:15 +0000 (UTC)
From: =?utf-8?Q?Jean-Baptiste_Onofr=C3=A9_=28JIRA=29?= <jira@apache.org>
To: issues@karaf.apache.org
Message-ID: <JIRA.12618497.1354469956054.231418.1366983495791@arcas>
In-Reply-To: <JIRA.12618497.1354469956054@arcas>
References: <JIRA.12618497.1354469956054@arcas>
Subject: [jira] [Commented] (KARAF-2044) Provide the ability to edit text
 resources from the Karaf shell
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/KARAF-2044?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1364=
2842#comment-13642842 ]=20

Jean-Baptiste Onofr=C3=A9 commented on KARAF-2044:
---------------------------------------------

jledit has been included in 3.0.0.RC1. I just let this Jira open for review=
.
               =20
> Provide the ability to edit text resources from the Karaf shell
> ---------------------------------------------------------------
>
>                 Key: KARAF-2044
>                 URL: https://issues.apache.org/jira/browse/KARAF-2044
>             Project: Karaf
>          Issue Type: New Feature
>          Components: karaf-shell
>            Reporter: Ioannis Canellos
>            Assignee: Ioannis Canellos
>             Fix For: 3.0.0
>
>         Attachments: KARAF-20441.patch, KARAF-2044-2.patch, KARAF-2044-ka=
raf_2_3_x.patch, KARAF-2044-karaf_trunk.patch
>
>
> It would be awesome if we could edit text resources from inside the Karaf=
 shell.
> Why?
> i) Because I won't have to quit the console, or open a new term/ssh sessi=
on to modify the resource.
> ii) Editing config files via config:edit or jaas:manage, is workable but =
not perfect.
> iv) Configs are not only cfg files, in many cases we also have xml (jetty=
.xml, broker.xml, hazelcast.xml).
> iv) Integrating such feature with the url handlers would just rock (e.g. =
modify the content of cloud blob or a zookeeper znode, without having to ma=
nually copy the content locally edit and reupload).
> =20
> How?
> I haven't found so far a decent oss console based editor in java. So, our=
 best bet is to integrate with console editors already present in the syste=
m (e.g. vi, nano, emacs, edit etc).

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