Let’s try again…
What I’m proposing here does not move any sources to different repos or change
how e.g. the spring-boot tables of components etc are generated. I think it’s
completely appropriate for the code generation etc for camel-spring-boot and
camel-karat to be in separate
This is another issue, but I’m thinking about it :-)
David Jencks
> On Oct 5, 2021, at 12:26 AM, Claus Ibsen wrote:
>
> Hi
>
> Btw on another note, then we have for camel-spring-boot and
> camel-karaf a "catalog" which holds JSon files with information for
> every JAR they support.
>
>
Hi
Btw on another note, then we have for camel-spring-boot and
camel-karaf a "catalog" which holds JSon files with information for
every JAR they support.
https://github.com/apache/camel-spring-boot/tree/main/catalog/camel-catalog-provider-springboot
The same for karaf at
Hi David
Can you explain in more detail what you mean by moving "information"
to "components".
If you refer to that there is a .adoc file that is generating a big
table such as
https://raw.githubusercontent.com/apache/camel-spring-boot/main/docs/modules/ROOT/pages/list.adoc
Then that is
IIUC the camel-karaf and camel-spring-boot subprojects are always released in
sync with main camel.
On the websites, for these subprojects, there is a little bit of general
information, and some tables listing the parts of the “components” that are
supported in the subproject (components,
