[ 
https://issues.apache.org/jira/browse/KARAF-779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13073176#comment-13073176
 ] 

Glen Mazza commented on KARAF-779:
----------------------------------

It's not just top or bottom--since you can have multiple sources of custom info 
data you'll probably want the ability to arrange the multiple sources as well.

Perhaps a priority level should be added to both the Karaf-Info manifest entry 
and the InfoProvider interface (the two ways to add custom information right 
now).

There are many ways to do the priority numbering.  Here's one possibility: the 
current Karaf default info would have always have a priority of zero, anything 
you want "on top" would have a negative priority number (the more negative, the 
more "on top"), anything you'd want at the bottom would have a positive 
priority number (the larger the number the more at the bottom.)  If not 
provided, the default priority level for any custom info would be "1", meaning 
it's placed at the end of the standard info.  Further the specific ordering of 
any custom info sharing the same priority is undefined -- customs infos with 
the same priority can go in any order alongside other custom infos that share 
the same priority level.

With just one person requesting this, the above is quite possibly overkill. 
OTOH this is functionality that enhances Karaf's branding capabilities.


> Set Priority for InfoProvider
> -----------------------------
>
>                 Key: KARAF-779
>                 URL: https://issues.apache.org/jira/browse/KARAF-779
>             Project: Karaf
>          Issue Type: New Feature
>          Components: karaf-shell
>    Affects Versions: 2.2.2
>            Reporter: Philipp Hönisch
>            Priority: Trivial
>
> It is possible to extend the karaf info command with custom information and 
> it would be great to define the priority it, e.g. if the info should be added 
> at the top or bottom of the list.

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


Reply via email to