Runtime artifact's POM repos aren't propagated to resolve the corresponding deployment deps

[lburgazzoli]

Describe the bug
I'm testing camel extensions against the latest quarkus snapshot to validate the fix for #3094 and when running the integration tests I see the following error:

[INFO] Running org.apache.camel.quarkus.core.CamelTest
[ERROR] Tests run: 3, Failures: 0, Errors: 3, Skipped: 0, Time elapsed: 28.218 s <<< FAILURE! - in org.apache.camel.quarkus.core.CamelTest
[ERROR] testProperties  Time elapsed: 0.008 s  <<< ERROR!
org.junit.jupiter.api.extension.TestInstantiationException: TestInstanceFactory [io.quarkus.test.junit.QuarkusTestExtension] failed to instantiate test class [org.apache.camel.quarkus.core.CamelTest]: Failed to create the boostrap class loader
Caused by: java.lang.IllegalStateException: Failed to create the boostrap class loader
Caused by: io.quarkus.bootstrap.BootstrapException: Failed to create the deployment classloader for org.apache.camel.quarkus:camel-quarkus-integration-test-core::jar:0.0.1-SNAPSHOT
Caused by: io.quarkus.bootstrap.resolver.AppModelResolverException: Failed to inject extension deployment dependencies for org.apache.camel.quarkus:camel-quarkus-integration-test-core:jar:0.0.1-SNAPSHOT
Caused by: io.quarkus.bootstrap.BootstrapDependencyProcessingException: No dependencies collected for Quarkus extension deployment artifact io.quarkus:quarkus-resteasy-deployment:jar:999-SNAPSHOT while at least the corresponding runtime artifact io.quarkus:quarkus-resteasy:jar:999-20190718.021121-60 is expected

To Reproduce
Steps to reproduce the behavior:

1. check-out https://github.com/lburgazzoli/apache-camel-quarkus/tree/test-packages
2. run ./mvnw clean install

Environment (please complete the following information):

• Output of uname -a or ver:

Linux mars 5.1.17-300.fc30.x86_64 #1 SMP Wed Jul 10 15:20:27 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

• Output of java -version:

openjdk version "1.8.0_212"
OpenJDK Runtime Environment (build 1.8.0_212-b04)
OpenJDK 64-Bit Server VM (build 25.212-b04, mixed mode)

• GraalVM version (if different from Java):

openjdk version "1.8.0_212"
OpenJDK Runtime Environment (build 1.8.0_212-20190523183340.buildslave.jdk8u-src-tar--b03)
OpenJDK 64-Bit GraalVM CE 19.0.2 (build 25.212-b03-jvmci-19-b04, mixed mode)

• Quarkus version or git rev:

999-SNAPSHOT (from oss snapshot repo)

[lburgazzoli]

Seems to be related to snapshots, testing against the latest quarkus bits built locally does not fail

[lburgazzoli]

So I've cleaned up my repo and tested it against snapshots from oss repo and the problems has materialized again so maybe the snapshots are corrupted

/cc @aloubyansky

[lburgazzoli]

Tested against new snapshots on a clean repo, same error:

[ERROR] testProperties  Time elapsed: 0.013 s  <<< ERROR!
org.junit.jupiter.api.extension.TestInstantiationException: TestInstanceFactory [io.quarkus.test.junit.QuarkusTestExtension] failed to instantiate test class [org.apache.camel.quarkus.core.CamelTest]: Failed to create the boostrap class loader
Caused by: java.lang.IllegalStateException: Failed to create the boostrap class loader
Caused by: io.quarkus.bootstrap.BootstrapException: Failed to create the deployment classloader for org.apache.camel.quarkus:camel-quarkus-integration-test-core::jar:0.0.1-SNAPSHOT
Caused by: io.quarkus.bootstrap.resolver.AppModelResolverException: Failed to inject extension deployment dependencies for org.apache.camel.quarkus:camel-quarkus-integration-test-core:jar:0.0.1-SNAPSHOT
Caused by: io.quarkus.bootstrap.BootstrapDependencyProcessingException: No dependencies collected for Quarkus extension deployment artifact io.quarkus:quarkus-resteasy-deployment:jar:999-SNAPSHOT while at least the corresponding runtime artifact io.quarkus:quarkus-resteasy:jar:999-20190719.021155-61 is expected

[lburgazzoli]

For more info see:

• Move test packages to org.apache.camel apache/camel-quarkus#77
• https://builds.apache.org/job/camel-quarkus-pr/22

[aloubyansky]

This issue is about propagating repositories from the runtime artifact's (effective) POM to the resolution of the deployment artifacts. This issue affects only Quarkus tests where we break from the Maven build context and initialize our own resolver. Which also means a possible workaround would be to mvn clean install -DskipTests first and then mvn test.