You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by GitBox <gi...@apache.org> on 2019/08/01 09:07:46 UTC

[GitHub] [camel-quarkus] ppalaga commented on issue #75: Include quarkus info in camel-catalog

ppalaga commented on issue #75: Include quarkus info in camel-catalog
URL: https://github.com/apache/camel-quarkus/issues/75#issuecomment-517198206
 
 
   Actually, what purpose should the Catalog serve? If the main use case is to answer the question 
   
   > For given component *c* and Camel version *x.y.z*, which platforms (SB, Quarkus, WidlFly, ...) are supported?
   
   then I think all the necessary info is already available on Maven Central. The answer can be obtained by a script that joins camel BOM with the compatible platform BOMs. So we perhaps do not need feed that information into a git repository? Well at least not manually. There could be a service or a regular job that would aggregate that info and make it available in some suitable format. WDYT?

----------------------------------------------------------------
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


With regards,
Apache Git Services