Re: [I] Various guide pages have been taken down for non-deprecated extensions [camel-quarkus]

2024-02-28 Thread via GitHub


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

   Many thanks @holly-cummins for taking care for this. I agree with James, 
that dropping dead links for Camel might be a good solution. They are indeed 
auto-generated following a pattern (with one or two exceptions).


-- 
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-unsubscr...@camel.apache.org

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



Re: [I] Various guide pages have been taken down for non-deprecated extensions [camel-quarkus]

2024-02-28 Thread via GitHub


jamesnetherton commented on issue #5814:
URL: https://github.com/apache/camel-quarkus/issues/5814#issuecomment-1968601425

   > Add an exception and silently drop dead links for Camel extensions only. 
This has the drawback that if a guides link on a new extension gets messed up 
(easily done), no one gets alerted
   
   I'd be ok with that. Not sure what others think.
   
   The messed up guides link issue should (hopefully) never be a problem for 
us. They are all auto generated and the doc file name follows a convention.
   
   > Something else?
   
   Maybe fall back to the raw AsciiDoc content on the release maintenance 
branch? E.g for Facebook:
   
   
https://github.com/apache/camel-quarkus/blob/3.6.x/docs/modules/ROOT/pages/reference/extensions/facebook.adoc
   
   Some of the links wont get rendered outside of the Camel website, but at 
least the core content should be there.


-- 
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-unsubscr...@camel.apache.org

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