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

Carsten Ziegeler edited comment on SLING-5188 at 10/23/15 6:33 AM:
-------------------------------------------------------------------

I think we should only move plugins to the "Sling" category which are really 
used by Sling. General stuff, like bundles from commons or the OSGi installer 
which can be used without Sling should be somewhere else. I guess topology is a 
grey area as it could be used without Sling but so far we don't have an 
independent implementation.

Or in other words, we should look at the categories more from the users 
perspective. For example, the OSGi installer is about ... OSGi, so we should 
put it into that category.


was (Author: cziegeler):
I think we should only move plugins to the "Sling" category which are really 
used by Sling. General stuff, like bundles from commons or the OSGi installer 
which can be used without Sling should be somewhere else. I guess topology is a 
grey area as it could be used without Sling but so far we don't have an 
independent implementation

> Some WebConsole plugins are placed in the 'main' category
> ---------------------------------------------------------
>
>                 Key: SLING-5188
>                 URL: https://issues.apache.org/jira/browse/SLING-5188
>             Project: Sling
>          Issue Type: Improvement
>    Affects Versions: Engine 2.4.4, Commons Mime 2.1.8, Auth Core 1.3.12, 
> Installer Console 1.0.0, Discovery Impl 1.1.8
>            Reporter: Robert Munteanu
>            Assignee: Robert Munteanu
>             Fix For: Commons Mime 2.1.10, Auth Core 1.3.14, Installer Console 
> 1.0.2, Discovery Impl 1.1.10, Engine 2.4.6
>
>
> Some WebConsole plugins don't specify a category and they end up in the 
> 'main' menu.
> They should be under Sling instead:
> - Authenticator
> - Mime Types
> - OSGi Installer
> - Recent Requests
> - Topoloy Management



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to