gsmet edited a comment on issue #3027: URL: https://github.com/apache/camel-quarkus/issues/3027#issuecomment-904498087
So the problem is that the `GcpConfigHolder` CDI bean (https://github.com/quarkiverse/quarkus-google-cloud-services/blob/main/common/runtime/src/main/java/io/quarkiverse/googlecloudservices/common/GcpConfigHolder.java#L6) is removed by ArC in `main` and not in older versions. If I make the `GcpConfigHolder` bean `@Unremovable`, things are working again. It's the second time someone complains about a CDI bean that is forcefully removed in `main` while it wasn't before. I think someone from the Optaplanner team also complained about something similar. I see the `GcpConfigHolder` bean being injected via annotations in some other beans but I have no idea if these beans are removed or not. I'm reproducing this by running the `camel-quarkus-integration-test-google-pubsub` tests (https://github.com/apache/camel-quarkus/tree/main/integration-tests/google-pubsub) with Quarkus 999-SNAPSHOT (changed in the parent pom). The log is all garbled but the bean Quarkus is complaining about is probably this one (and yes I have to figure out why the log is all garbled). @manovotn @mkouba does it ring a bell? Could you make sure it's not a bug? Given we have both Camel Quarkus and Optaplanner failing, it looks like it's worth digging. /cc @loicmathieu FYI, a quick fix is to make `GcpConfigHolder` `@Unremovable`. Maybe we should do that for now? -- 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
