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 2025/01/02 08:12:47 UTC

Re: [I] Unexpected route discovery behavior when "mixing" `routes-discovery.include-patterns` and bean scopes [camel-quarkus]

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

   Yes, this has been known for some time. It's a UX issue with the config that controls how routes are discovered.
   
   `quarkus.camel.routes-discovery.include-patterns` will operate on non-CDI bean `RouteBuilder` impls at build time.
   
   `camel.main.javaRoutesIncludePattern` will operate on CDI beans discovered via the Camel registry at run time. So currently, this is the config option to use if you want to ignore `RouteBuilder` classes that have bean annotations.
   
   


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