The org.wildfly.test.integration.microprofile.reactive.RunArtemisAmqpSetupTask in XP's testsuite/integration/microprofile attempts to launch an embedded AMQ, but doesn't declare a dependency on the google guava artifact it requires. This leaves it relying on a fragile transitive dependency chain like this:

+- org.wildfly.core:wildfly-model-test:jar:21.0.5.Final-redhat-00001:compile
[INFO] |  +- org.apache.maven:maven-resolver-provider:jar:3.5.4:compile
[INFO] |  |  +- org.apache.maven:maven-model:jar:3.5.4:compile
[INFO] |  |  +- org.apache.maven:maven-model-builder:jar:3.5.4:compile
[INFO] |  |  |  +- org.codehaus.plexus:plexus-interpolation:jar:1.24:compile
[INFO] |  |  |  +- org.codehaus.plexus:plexus-component-annotations:jar:1.7.1:compile
[INFO] |  |  |  +- org.apache.maven:maven-artifact:jar:3.5.4:compile
[INFO] |  |  |  +- org.apache.maven:maven-builder-support:jar:3.5.4:compile
[INFO] |  |  |  \- com.google.guava:guava:jar:32.1.1.jre-redhat-00001:compile

That breaks if xp-5.0.x is aligned with a later version of WildFly Core, e.g. as is contemplated with JBEAP-26950 or even with any simple update of the base EAP version in the xp-5.0.x root pom. For example, org.wildfly.core:wildfly-model-test:jar:21.0.8.Final-redhat-00001 does not bring in guava as a transitive dep.

The testsuite/integration/microprofile module should explicitly declare this dependency.