You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2023/08/09 09:15:00 UTC
[jira] [Updated] (CAMEL-17394) camel-core - Generate configurer metadata
[ https://issues.apache.org/jira/browse/CAMEL-17394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen updated CAMEL-17394:
--------------------------------
Fix Version/s: 4.x
(was: 3.x)
> camel-core - Generate configurer metadata
> -----------------------------------------
>
> Key: CAMEL-17394
> URL: https://issues.apache.org/jira/browse/CAMEL-17394
> Project: Camel
> Issue Type: New Feature
> Components: tooling
> Reporter: Claus Ibsen
> Priority: Major
> Fix For: 4.x
>
>
> We have more and more properties that can be set via camel-main.
> We can look at when using @Configurer to generate type-safe and reflection free configuration then we can also generate tooling metadata (json files) that we can use for the website and tooling.
> Today we generate a single camel-main json file that has all of them. But it may be worth to be able to externalize these into individual files, so we can have them seperated.
> For example dev consoles can likely be custom per component so they will not be in core, but in the component. And so it would be worth to have a way of generate tooling medata for them also.
> We can either consider a json file that is specific for a dev-console or something generic with configurer.
> Then we can see also if we can use this for dev consoles that can be made work in both jbang, main, quarkus and spring boot.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)