Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-19300

Missing test dependency on com.google.guava

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Minor Minor
    • 33.0.0.Beta1, 33.0.0.Final
    • None
    • None
    • None

      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:

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

      That broke downstream when a org.apache.maven:maven-model-builder update shifted to a version that did not transitively bring in guava.

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

              bstansbe@redhat.com Brian Stansberry
              bstansbe@redhat.com Brian Stansberry
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: