[
https://issues.apache.org/jira/browse/CAMEL-9131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14900537#comment-14900537
]
Claus Ibsen commented on CAMEL-9131:
------------------------------------
I added a check to the catalog so it reports components which has 20+ endpoint
options without any labels. Those components would be a good starting point to
get labelled as they have many options.
{code}
[INFO] Component with more than 20 unlabelled options: 28
[INFO] amqp
[INFO] cxf
[INFO] cxfrs
[INFO] facebook
[INFO] ftp
[INFO] ftps
[INFO] imap
[INFO] imaps
[INFO] jms
[INFO] jmx
[INFO] mina2
[INFO] mqtt
[INFO] netty
[INFO] netty-http
[INFO] netty4
[INFO] netty4-http
[INFO] pop3
[INFO] pop3s
[INFO] rabbitmq
[INFO] salesforce
[INFO] scp
[INFO] sftp
[INFO] sip
[INFO] sips
[INFO] smpp
[INFO] smpps
[INFO] smtp
[INFO] smtps
[INFO]
{code}
> Camel components - Add more labels to group the options
> -------------------------------------------------------
>
> Key: CAMEL-9131
> URL: https://issues.apache.org/jira/browse/CAMEL-9131
> Project: Camel
> Issue Type: Improvement
> Components: tooling
> Affects Versions: 2.16.0
> Reporter: Claus Ibsen
> Fix For: 2.16.0, 2.17.0
>
>
> See nabble
> http://camel.465427.n5.nabble.com/advanced-label-for-params-tp5771390.html
> We should add more labels to the various endpoint / component options os they
> can be grouped, eg when an endpoint has many options then maybe 50 options is
> listed in the same group. If we can figure out which options are
> - advanced
> - security
> - locking
> - threading
> etc then we can add such as labels. This will help group the options and make
> it easier for users to understand and use the components.
> Over time we should come up with a list of known names for these labels, so
> we reuse the same names.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
