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 https://github.com/apache/camel-karaf/tree/main/catalog/camel-catalog-provider-karaf If this is the case, then I think what you did for the core camel project was to use this to generate the list of components there. If this can be done the same way, then we can do it similarly, and we can then remove that maven plugin that generates that list.adoc file. On Tue, Oct 5, 2021 at 9:20 AM Claus Ibsen <[email protected]> wrote: > > 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 generated via a maven plugin, that scans the source code > and builds up that table. > > The list is then used on the website to list all the supported Spring > Boot starters. > https://camel.apache.org/camel-spring-boot/latest/list.html > > That list used the xref links like we do in other places for Camel > components, languages, data formats, etc. > What is it that goes against the meaning of an Antora component? > > IMHO the system we have with the maven plugin that generates that > single file works well. > And the docs are in the src/main/docs folder for each of those spring > boot starters. > So we can maintain it where it belongs. > > > > On Tue, Oct 5, 2021 at 8:26 AM David Jencks <[email protected]> wrote: > > > > 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, dataformats, etc). The table rows > > link to the docs in the “components” component, which is against the > > meaning of an Antora component. > > > > I wonder if it would make sense to include this subproject information in > > the “components” component. I’m thinking the nav might look like > > > > Components > > Dataformats > > Languages > > Other > > EIPS > > > > Camel-Spring-Boot > > - components > > - dataformats > > - languages > > - other > > > > Camel-Karaf > > - components > > - dataformats > > - languages > > - other > > > > I think this would be pretty easy to do, and it would definitely leave > > everything in the repo it is currently in. Does this idea seem interesting > > enough that I should prepare a PR/prototype? > > > > David Jencks > > > > -- > Claus Ibsen > ----------------- > http://davsclaus.com @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
