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

smallrye common Different artifacts version upstream vs RHBQ

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Blocker Blocker
    • None
    • 3.8.3.ER2
    • team/eng
    • None

      In latest build  https://download.eng.bos.redhat.com/rcm-guest/staging/quarkus/quarkus-platform-3.8.3.ER2/ there are some artifact which have different version then upstream (compared with 3.8.3 usptream version).

       

      io.smallrye.common:smallrye-common-classloader 2.1.2 2.2.0.redhat-00002
      io.smallrye.common:smallrye-common-constraint 2.1.2 2.2.0.redhat-00002
      io.smallrye.common:smallrye-common-cpu 2.1.2 2.2.0
      io.smallrye.common:smallrye-common-expression 2.1.2 2.2.0.redhat-00002
      io.smallrye.common:smallrye-common-function 2.1.2 2.2.0.redhat-00002
      io.smallrye.common:smallrye-common-io 2.1.2 2.2.0.redhat-00002
      io.smallrye.common:smallrye-common-net 2.1.2 2.2.0
      io.smallrye.common:smallrye-common-os 2.1.2 2.2.0.redhat-00002
      io.smallrye.common:smallrye-common-ref 2.1.2 2.2.0.redhat-00002
      io.smallrye.common:smallrye-common-version 2.1.2 2.2.0.redhat-00002
      io.smallrye.common:smallrye-common-vertx-context 2.1.2 2.2.0.redhat-00002

       
      It actually has to be fixed upstream. It appears there is some other BOM imported before smallrye-common-bom that brings in 2.1.2 upstream instead of 2.2.0. https://github.com/quarkusio/quarkus/pull/39826 will fix it upstream

      comment by olubyans@redhat.com 

              Unassigned Unassigned
              sausingh@redhat.com Saumya Singh
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: