You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by GitBox <gi...@apache.org> on 2020/09/24 14:37:38 UTC

[GitHub] [camel-quarkus] ppalaga commented on issue #1795: Generate partials instead of pages for the individual Camel bits

ppalaga commented on issue #1795:
URL: https://github.com/apache/camel-quarkus/issues/1795#issuecomment-698386731


   > there could be two camel-quarkus author mode playbooks, one quarks-only and the other including the main components component.
   
   I went with this option after discussing it with @jamesnetherton . I have updated https://github.com/apache/camel-quarkus/pull/1814
   
   
   
   > I don’t think it’s appropriate to fail a partial site build based on broken xrefs. This would mean that one part of the documentation can’t refer to another part. If there’s an agreed upon principle that there shouldn’t be cross-(antora-)component xrefs, it needs to be clearly stated somewhere :-)
   
   That's our current _modus operandi_ Changing it would require a separate discussion.
   
   > The include in the main camel component docs means that it would be easy to include a generated line, either “this component is in the camel-quarkus XXX extension” or “this component is not available in camel-quarkus”. 
   
   Yeah, that's an important advantage of using partials (thanks again for proposing it!). I am going to file a PR against Camel once #1814 is merged.


----------------------------------------------------------------
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:
users@infra.apache.org