[jira] [Commented] (CAMEL-17404) [Docs][camel-karaf]Generate components table with Antora

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CAMEL-17404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17467561#comment-17467561 ] 

ASF GitHub Bot commented on CAMEL-17404:
----------------------------------------

djencks opened a new pull request #745:
URL: https://github.com/apache/camel-website/pull/745


   Preview of changes for https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-17404


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> [Docs][camel-karaf]Generate components table with Antora
> --------------------------------------------------------
>
>                 Key: CAMEL-17404
>                 URL: https://issues.apache.org/jira/browse/CAMEL-17404
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-karaf
>            Reporter: David Jencks
>            Assignee: David Jencks
>            Priority: Major
>
> I propose removing the java code generating the tables on the components page and replacing it with Antora generation.  This involves:
> - generating the .json files for components into the catalog src directory, and committing them. Generation is fairly easy, but at the moment committing is a manual process.  On main, changes should end up in the auto-generated PR, but on other branches no such mechanism is in place, resulting in at least two branches having uncommitted changes after builds (before my changes).
> - removing the mojo to generate the table contents
> - adding a little javascript to help with the table entries
> - using the indexer extension to generate the tables from the .json files.
> In my PRs, I've changed the tables a little bit:
> - the feature name is in it's own column, named "feature" rather than being in parentheses after the extension name (I had no idea what it meant)
> - the syntax string is removed.  I can't see how it can be useful in the table, but it if is it's easy enough to add.  I would expect that much more information about the extension would be needed to use it in karaf, just like in Spring.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)