-
Bug
-
Resolution: Done
-
Minor
-
2.7.5.ER4, 2.13.3.ER3
-
None
jetty version in smallrye-graphql and smallrye-opentracing are not aligned, causing duplicated jetty-bom
grep -l 9.4.44.v20210927-redhat-00001 . -R ./maven-repository/org/eclipse/jetty/jetty-bom/9.4.44.v20210927-redhat-00001/jetty-bom-9.4.44.v20210927-redhat-00001.pom ./maven-repository/io/smallrye/smallrye-graphql-parent/1.4.3.redhat-00001/smallrye-graphql-parent-1.4.3.redhat-00001.pom grep -l 9.4.38.v20210224-redhat-00001 . -R ./maven-repository/org/eclipse/jetty/jetty-bom/9.4.38.v20210224-redhat-00001/jetty-bom-9.4.38.v20210224-redhat-00001.pom ./maven-repository/io/smallrye/smallrye-opentracing-parent/2.0.1.redhat-00008/smallrye-opentracing-parent-2.0.1.redhat-00008.pom
As the duplicated artifact is BOM, we can whitelist that in Marete checks, BOMs and parent poms are kinda allowed duplicates, but it would be better to have the version in sync.
please sync the version of netty used in smallrye-opentracing with the version used in smallrye-graphql
- links to
-
RHSA-2023:120897
Red Hat build of Quarkus 3.2.6 release and security update