Unexpected route discovery behavior when "mixing" routes-discovery.include-patterns and bean scopes

[x80486]

Bug description

I think there may be an (unintended) issue regarding route discovery 🤔

I configured quarkus.camel.routes-discovery.include-patterns setting to control which routes should be discovered:

quarkus:
  camel:
    routes-discovery:
      enabled: true
      include-patterns:
        - tld/domain/route/* # Routes defined in tld.domain.route package

With this configuration, I would expect that no routes, other than the ones defined in include-patterns, will be discovered. This works fine as long as there aren't any RouteBuilder classes with bean-scoped annotations — they will be included as well, regardless of the aforementioned settings.

Is this behavior intended, or could it be considered a bug? I was under the assumption that include-patterns will strictly limit the discovery.

I have reviewed the documentation but could not find any specific mention of this behavior.

[jamesnetherton]

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.