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

Partial productization of Quarkus artifacts causes breaks dependency convergence in CEQ

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 2.7.5.GA, 2.7.5.ER3
    • None
    • team/eng
    • None

      quarkus-devtools-utilities is productized, quarkus-junit5-internal is not and therefore quarkus-junit5-internal pulls the community version of quarkus-devtools-utilities:

      Dependency convergence error for io.quarkus:quarkus-devtools-utilities:2.2.5.Final-redhat-00008 paths to dependency are:
+-org.apache.camel.quarkus:camel-quarkus-core-deployment:2.2.1-SNAPSHOT
  +-io.quarkus:quarkus-core-deployment:2.2.5.Final-redhat-00008
    +-io.quarkus:quarkus-devtools-utilities:2.2.5.Final-redhat-00008
and
+-org.apache.camel.quarkus:camel-quarkus-core-deployment:2.2.1-SNAPSHOT
  +-io.quarkus:quarkus-junit5-internal:2.2.5.Final
    +-io.quarkus:quarkus-devtools-utilities:2.2.5.Final
[WARN] Rule 1: org.apache.maven.plugins.enforcer.DependencyConvergence failed with message:

      I wonder whether it would be possible to start managing io.quarkus:quarkus-devtools-utilities and other artifacts that can induce the same problem in quarkus-bom?

            olubyans@redhat.com Alexey Loubyansky
            ppalaga Peter Palaga
            Pablo Gonzalez Granados Pablo Gonzalez Granados (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: