Mailing-List: contact issues-help@karaf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@karaf.apache.org
Date: Mon, 30 May 2011 14:25:47 +0000 (UTC)
From: "Andreas Pieber (JIRA)" <jira@apache.org>
To: issues@karaf.apache.org
Message-ID: 
 <1659124457.53461.1306765547426.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <630956213.9991.1305289487397.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (KARAF-638) Use the same naming convention in
 commands
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/KARAF-638?page=3Dcom.atlassian.=
jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D13041=
141#comment-13041141 ]=20

Andreas Pieber commented on KARAF-638:
--------------------------------------

how would this look for the log command (for example):

log (=3D=3D log:display)
log set TRACE (log:set TRACE)
log exception (or rather log display exception?)
....

Right?

Basically this looks nice and remembers me somehow of git (git branch, git =
branch -D ...)

Although this sounds nice I'm not sure how many changes will be required to=
 introduce this change into the current code?


> Use the same naming convention in commands
> ------------------------------------------
>
>                 Key: KARAF-638
>                 URL: https://issues.apache.org/jira/browse/KARAF-638
>             Project: Karaf
>          Issue Type: Improvement
>          Components: console
>            Reporter: Jean-Baptiste Onofr=C3=A9
>             Fix For: 3.0.0
>
>
> In Karaf commands, we should use the same naming convention.
> For instance, we have commands looking like:
> admin:change-rmi-server-port
> admin:change-rmi-registry-port
> dev:create-dump
> and others looking like:
> roleadd
> roledel
> features:listversions
> To be clear for the users, I propose to adopt the same naming convention =
for all commands, like:
> role-add
> role-del
> features:list-versions

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira