djencks commented on issue #1795: URL: https://github.com/apache/camel-quarkus/issues/1795#issuecomment-695142592
I got this idea to (mostly) work, and I think it may show up a problem with the current implementation. My work is on partial-components branch in https://github.com/djencks/camel-quarkus.git and https://github.com/djencks/camel.git. The local antora-playbook.yml in the camel-quarkus repo is set to build if the camel-quarkus and camel repos are checked out next to one another. The current components page is at <repo>/docs/target/site/camel-quarkus/latest/reference/components-2.html. I think the list of components is incomplete. For instance, there's only one atomix component listed whereas in my implementation there are six, which corresponds to the atomix extension. I also altered the extension page generation to use xrefs to the base camel component pages rather than https: links. This change should be made no matter what happens with this experiment. There's currently a problem in that there are a ton of missing include warnings for components that are not yet in camel-quarkus. This can be fixed by either: - generating a partial in camel-quarkus for every component/databinding/language/other whether or not it's supported yet; the partials for unsupported would be blank - waiting for https://gitlab.com/antora/antora/-/issues/678. If this approach seems like a good idea I can presumably do the dataformats/languages/other pages in the same way. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
