You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by "jamesnetherton (via GitHub)" <gi...@apache.org> on 2023/08/23 07:33:33 UTC

[GitHub] [camel-quarkus] jamesnetherton opened a new issue, #5214: FastComponentNameResolver component names should be populated from included component service paths

jamesnetherton opened a new issue, #5214:
URL: https://github.com/apache/camel-quarkus/issues/5214

   ### Describe the feature here
   
   Right now the Camel catalog is inspected at build time to get the component names. Which works so long as a component is present in the catalog. It'd be better to scan for `META-INF/services/org/apache/camel/component/*`. That way a component does not need to be present in the Camel catalog and features like excluding service patterns can be taken into account.
   


-- 
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.apache.org

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


[GitHub] [camel-quarkus] jamesnetherton closed issue #5214: FastComponentNameResolver component names should be populated from included component service paths

Posted by "jamesnetherton (via GitHub)" <gi...@apache.org>.
jamesnetherton closed issue #5214: FastComponentNameResolver component names should be populated from included component service paths
URL: https://github.com/apache/camel-quarkus/issues/5214


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