[Quarkus 2.4.0] Messaging tests fail with ambiguous dependencies for org.apache.camel.quarkus.component.messaging.it.util.scheme.ComponentScheme

[jamesnetherton]

Maybe something changed recently in Quarkus that has started causing this error.

What confuses me is that the nightly Quarkus platform builds with 999-SNAPSHOT & CQ 2.3.0 are passing. I'd expect to see the same failure.

2021-10-11T03:31:18.4927883Z java.lang.RuntimeException: 
2021-10-11T03:31:18.4935938Z java.lang.RuntimeException: io.quarkus.builder.BuildException: Build failure: Build failed due to errors
2021-10-11T03:31:18.4948543Z 	[error]: Build step io.quarkus.arc.deployment.ArcProcessor#validate threw an exception: javax.enterprise.inject.spi.DeploymentException: Found 14 deployment problems: 
2021-10-11T03:31:18.4960185Z [1] Ambiguous dependencies for type org.apache.camel.quarkus.component.messaging.it.util.scheme.ComponentScheme and qualifiers [@Default]
2021-10-11T03:31:18.4970629Z 	- java member: org.apache.camel.quarkus.component.messaging.it.MessagingCommonResource#componentScheme
2021-10-11T03:31:18.4989377Z 	- declared on CLASS bean [types=[org.apache.camel.quarkus.component.messaging.it.MessagingCommonResource, java.lang.Object], qualifiers=[@Default, @Any], target=org.apache.camel.quarkus.component.messaging.it.MessagingCommonResource]
2021-10-11T03:31:18.4994409Z 	- available beans:
2021-10-11T03:31:18.5106045Z 		- PRODUCER METHOD bean [types=[org.apache.camel.quarkus.component.messaging.it.util.scheme.ComponentScheme, java.lang.Object], qualifiers=[@Default, @Any], target=org.apache.camel.quarkus.component.messaging.it.util.scheme.ComponentScheme getMessagingComponentScheme(org.apache.camel.CamelContext camelContext), declaringBean=org.apache.camel.quarkus.component.messaging.it.util.scheme.MessagingComponentSchemeProducer]
2021-10-11T03:31:18.5142671Z 		- PRODUCER METHOD bean [types=[org.apache.camel.quarkus.component.messaging.it.util.scheme.ComponentScheme, java.lang.Object], qualifiers=[@Default, @Any], target=org.apache.camel.quarkus.component.messaging.it.util.scheme.ComponentScheme getMessagingComponentScheme(org.apache.camel.CamelContext camelContext), declaringBean=org.apache.camel.quarkus.component.messaging.it.util.scheme.MessagingComponentSchemeProducer]

[mkouba]

I believe that a similar problem was fixed in quarkusio/quarkus#20582. Exactly what version of quarkus do you use?

[jamesnetherton]

@mkouba It fails with 2.4.0.CR1 and the latest 999-SNAPSHOT. It was working fine in previous versions.

To replicate, the working branch of the 2.4.0 upgrade is here:

https://github.com/jamesnetherton/camel-quarkus/tree/quarkus-2.4.0.CR1

Build the project then change into integration-tests/jms-artemis-client and do mvn clean test.

[jamesnetherton]

FWIW - I can probably work around this by removing the CDI producers + injection points and replacing it with something else.

Obviously that's not ideal, as there'd still potentially be some issue in Quarkus left unresolved.

[aloubyansky]

It may be related to my bootstrap refactoring PR. I'll check whether it's a regression.

[mkouba]

Hm, so I built the project with -Denforcer.skip and got [ERROR] Failed to execute goal com.github.eirslett:frontend-maven-plugin:1.6:yarn (antora-xref-check) on project camel-quarkus-docs but still I was able to run the tests for jms-artemis-client and from the debug log I can see that the bean classes, e.g. org.apache.camel.quarkus.component.messaging.it.util.scheme.MessagingComponentSchemeProducer, are found twice in the bean archive index. Which could mean that an ApplicationArchive is built twice from a dependency or there are two dependencies that contain the given class.

[aloubyansky]

I am building it now.

[aloubyansky]

I know what the problem is, this is mine.

[jamesnetherton]

Verified as fixed in #3210.