Uploaded image for project: 'Quarkus'
  1. Quarkus
  2. QUARKUS-2587

maven repository does not contain org.amqphub.quarkus:quarkus-qpid-jms-bom:pom:0.32.0.redhat-00002

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Blocker Blocker
    • 2.7.6.SP2.GA, 2.7.6.SP2.CR2
    • 2.7.6.SP1.GA, 2.7.6.SP2.CR1
    • None
    • None
    • False
    • None
    • False
    • ---

      Raising a new JIRA based on QUARKUS-2505 around https://issues.redhat.com/browse/QUARKUS-2505?focusedCommentId=21184695&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-21184695 specifically, as requested on mailing lists.

      QUARKUS-2505 initially reported that the quarkus platform boms used the 0.32.0.redhat-00001 build of quarkus-qpid-jms, while the maven repository [zip] contained 0.32.0.redhat-00002 instead (following QUARKUS-2442), meaning use of the extension didnt work. As part of rhn-support-shiggs analysis he tried instead to use the 0.32.0.redhat-00002 version that the maven repo included and commented that still didnt work with the output showing this was because org.amqphub.quarkus:quarkus-qpid-jms-bom:pom:0.32.0.redhat-00002 could not be found in the maven repo:

      Downloading from redhat: https://maven.repository.redhat.com/ga/org/amqphub/quarkus/quarkus-qpid-jms-bom/0.32.0.redhat-00002/quarkus-qpid-jms-bom-0.32.0.redhat-00002.pom
Downloading from central: https://repo.maven.apache.org/maven2/org/amqphub/quarkus/quarkus-qpid-jms-bom/0.32.0.redhat-00002/quarkus-qpid-jms-bom-0.32.0.redhat-00002.pom
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  3.642 s
[INFO] Finished at: 2022-10-18T13:21:52-04:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project code-with-quarkus: Could not resolve dependencies for project com.redhat.support.examples:code-with-quarkus:jar:1.0.0-SNAPSHOT: Failed to collect dependencies at org.amqphub.quarkus:quarkus-qpid-jms:jar:0.32.0.redhat-00002: Failed to read artifact descriptor for org.amqphub.quarkus:quarkus-qpid-jms:jar:0.32.0.redhat-00002: Could not find artifact org.amqphub.quarkus:quarkus-qpid-jms-bom:pom:0.32.0.redhat-00002 in maven.central (https://repo1.maven.org/maven2) -> [Help 1]

      The 0.32.0.redhat-00001 vs 0.32.0.redhat-00002 mismatch issue in the platform boms vs maven repo was resolved in 2.7.6 SP2.CR1, however the second issue of org.amqphub.quarkus:quarkus-qpid-jms-bom:pom:0.32.0.redhat-00002 being missing from the maven repo still remains, which I similarly hit when trying out the 2.7.6 SP2.CR1 maven repo zip.

      Failed to collect dependencies at org.amqphub.quarkus:quarkus-qpid-jms:jar:0.32.0.redhat-00002: Failed to read artifact descriptor for org.amqphub.quarkus:quarkus-qpid-jms:jar:0.32.0.redhat-00002: Could not find artifact org.amqphub.quarkus:quarkus-qpid-jms-bom:pom:0.32.0.redhat-00002 in red-hat-enterprise-maven-repository (file:///path/to/extracted/rh-quarkus-platform-2.7.6.SP2-maven-repository/maven-repository)

      The missing file was productized and is in the indy/pnc repo containing the original build, http://indy.psi.redhat.com/browse/maven/hosted/pnc-builds/org/amqphub/quarkus/quarkus-qpid-jms-bom/0.32.0.redhat-00002/. Adding the indy repo to mavens settings, it does then find the file and things work.

              varjain@redhat.com Vardhman Jain
              gemmellr Robbie Gemmell
              Pablo Gonzalez Granados Pablo Gonzalez Granados (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: