[
https://issues.apache.org/jira/browse/CAMEL-11675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16531276#comment-16531276
]
ASF GitHub Bot commented on CAMEL-11675:
----------------------------------------
davsclaus commented on issue #2391: CAMEL-11675 - Repetable @Metadata
annotation and amend apt for tooling
URL: https://github.com/apache/camel/pull/2391#issuecomment-402134226
Does this not require to have a key or some id like attribute on `@Metadata`
as in the JIRA ticket? Also the apt plugin should favour the metadata that has
no value set in key, as that is what its using by default for all the component
json data stuff it does, eg
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> @Metadata should be repeatable
> ------------------------------
>
> Key: CAMEL-11675
> URL: https://issues.apache.org/jira/browse/CAMEL-11675
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Reporter: Luca Burgazzoli
> Priority: Minor
> Fix For: 2.23.0
>
>
> As today @Metadata is not repeatable so it is not easy to add multiple
> information to i.e. a component, it would be nice to write something like:
> {code:java}
> @Metadata(key = "platforms", enums = { "spring", "spring-boot", "osgi" })
> @Metadata(key = "extensions", types = { MyExtension.cass })
> class MyComponent extends DefaultComponent {
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
