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

Artifact quarkus-tls-registry-cli is a shaded jar but has issues with dependency resolution by jbang

XMLWordPrintable

    • False
    • None
    • False
    • +
    • Hide

      acquire the product Maven repository zip file and unzip it, then

      wget -O /home/hudson/.m2/settings.xml https://gitlab.cee.redhat.com/quarkus-qe/jenkins-jobs/-/raw/main/jobs/rhbq/files/settings.xml
      
      unzip -qo quarkus-maven-repo.zip
      
      sed -i -e 's|/path_to_repo|$PWD/rh-quarkus-platform-3.15.1.GA-maven-repository/maven-repository/|' /home/hudson/.m2/settings.xml
      
      mkdir -p /home/hudson/.quarkus/
      
      cat <<EOF > ~/.quarkus/config.yaml
      ---
      registries:
      - registry-3-15-1-redhat-00002.apps.ocp-c1.prod.psi.redhat.com:
          update-policy: "always"
          descriptor:
            artifact: "com.redhat.psi.prod.ocp-c1.apps.registry-3-15-1-redhat-00002:quarkus-registry-descriptor::json:1.0-SNAPSHOT"
          maven:
            repository:
              url: "https://registry-3-15-1-redhat-00002.apps.ocp-c1.prod.psi.redhat.com/maven"
      - registry.quarkus.redhat.com
      - registry.quarkus.io
      EOF
      
      jbang config set run.repos file://${PATH_TO_UNZIPPED_REPO}
      
      quarkus create app reproducer --stream=3.15 -x=quarkus-rest -Dquarkus.analytics.disabled=true
      
      cd reproducer
      
      quarkus tls generate-quarkus-ca --truststore -r --verbose 
      
      Show
      acquire the product Maven repository zip file and unzip it, then wget -O /home/hudson/.m2/settings.xml https: //gitlab.cee.redhat.com/quarkus-qe/jenkins-jobs/-/raw/main/jobs/rhbq/files/settings.xml unzip -qo quarkus-maven-repo.zip sed -i -e 's|/path_to_repo|$PWD/rh-quarkus-platform-3.15.1.GA-maven-repository/maven-repository/|' /home/hudson/.m2/settings.xml mkdir -p /home/hudson/.quarkus/ cat <<EOF > ~/.quarkus/config.yaml --- registries: - registry-3-15-1-redhat-00002.apps.ocp-c1.prod.psi.redhat.com:     update-policy: "always"     descriptor:       artifact: "com.redhat.psi.prod.ocp-c1.apps.registry-3-15-1-redhat-00002:quarkus-registry-descriptor::json:1.0-SNAPSHOT"     maven:       repository:         url: "https: //registry-3-15-1-redhat-00002.apps.ocp-c1.prod.psi.redhat.com/maven" - registry.quarkus.redhat.com - registry.quarkus.io EOF jbang config set run.repos file: //${PATH_TO_UNZIPPED_REPO} quarkus create app reproducer --stream=3.15 -x=quarkus- rest -Dquarkus.analytics.disabled= true cd reproducer quarkus tls generate-quarkus-ca --truststore -r --verbose
    • ---

      Trying to run tests with quarkus-tls-registry-cli in 3.15.1.CR1 resulted in the following failures:

      Could not resolve dependencies: The following artifacts could not be resolved: com.fasterxml.jackson.core:jackson-core:jar:2.16.1.redhat-00003 (absent), org.jboss.logging:jboss-logging:jar:3.5.3.Final-redhat-00001 (absent), org.wildfly.common:wildfly-common:jar:1.6.0.Final-redhat-00001 (absent): Could not find artifact com.fasterxml.jackson.core:jackson-core:jar:2.16.1.redhat-00003 in central
      

      Those are not part of 3.15.1.CR1 build, which leads me to believe they're not aligned to platform.

      The much weirder is the fact that trying to see dependency tree of the given pom results in the following:

      [INFO] io.quarkus:quarkus-tls-registry-cli:jar:3.15.1.redhat-00003
      [INFO] +- info.picocli:picocli:jar:4.7.6.redhat-00001:compile
      [INFO] +- io.smallrye.certs:smallrye-certificate-generator:jar:0.8.1:compile
      [INFO] |  +- org.bouncycastle:bcprov-jdk18on:jar:1.78.1.redhat-00002:compile
      [INFO] |  +- org.bouncycastle:bcpkix-jdk18on:jar:1.78.1.redhat-00002:compile
      [INFO] |  |  \- org.bouncycastle:bcutil-jdk18on:jar:1.78.1.redhat-00002:compile
      [INFO] |  +- io.smallrye.common:smallrye-common-os:jar:2.6.0.redhat-00001:compile
      [INFO] |  \- com.googlecode.plist:dd-plist:jar:1.28:compile
      [INFO] +- io.vertx:vertx-web-client:jar:4.5.10.redhat-00001:compile
      [INFO] |  +- io.vertx:vertx-uri-template:jar:4.5.10.redhat-00001:compile
      [INFO] |  +- io.vertx:vertx-web-common:jar:4.5.10.redhat-00001:compile
      [INFO] |  +- io.vertx:vertx-auth-common:jar:4.5.10.redhat-00001:compile
      [INFO] |  \- io.vertx:vertx-core:jar:4.5.10.redhat-00001:compile
      [INFO] |     +- io.netty:netty-common:jar:4.1.111.Final-redhat-00002:compile
      [INFO] |     +- io.netty:netty-buffer:jar:4.1.111.Final-redhat-00002:compile
      [INFO] |     +- io.netty:netty-transport:jar:4.1.111.Final-redhat-00002:compile
      [INFO] |     +- io.netty:netty-handler:jar:4.1.111.Final-redhat-00002:compile
      [INFO] |     |  +- io.netty:netty-transport-native-unix-common:jar:4.1.111.Final-redhat-00002:compile
      [INFO] |     |  \- io.netty:netty-codec:jar:4.1.111.Final-redhat-00002:compile
      [INFO] |     +- io.netty:netty-handler-proxy:jar:4.1.111.Final-redhat-00002:compile
      [INFO] |     |  \- io.netty:netty-codec-socks:jar:4.1.111.Final-redhat-00002:compile
      [INFO] |     +- io.netty:netty-codec-http:jar:4.1.111.Final-redhat-00002:compile
      [INFO] |     +- io.netty:netty-codec-http2:jar:4.1.111.Final-redhat-00002:compile
      [INFO] |     +- io.netty:netty-resolver:jar:4.1.111.Final-redhat-00002:compile
      [INFO] |     +- io.netty:netty-resolver-dns:jar:4.1.111.Final-redhat-00002:compile
      [INFO] |     |  \- io.netty:netty-codec-dns:jar:4.1.111.Final-redhat-00002:compile
      [INFO] |     \- com.fasterxml.jackson.core:jackson-core:jar:2.17.2.redhat-00001:compile
      [INFO] +- org.wildfly.security:wildfly-elytron-x500-cert-acme:jar:2.5.1.Final-redhat-00001:compile
      [INFO] |  +- org.wildfly.security:wildfly-elytron-asn1:jar:2.5.1.Final-redhat-00001:compile
      [INFO] |  |  \- org.jboss.logging:jboss-logging:jar:3.6.0.Final-redhat-00001:compile
      [INFO] |  +- org.wildfly.security:wildfly-elytron-base:jar:2.5.1.Final-redhat-00001:compile
      [INFO] |  +- org.wildfly.security:wildfly-elytron-x500:jar:2.5.1.Final-redhat-00001:compile
      [INFO] |  +- org.wildfly.security:wildfly-elytron-x500-cert:jar:2.5.1.Final-redhat-00001:compile
      [INFO] |  +- org.wildfly.security:wildfly-elytron-x500-cert-util:jar:2.5.1.Final-redhat-00001:compile
      [INFO] |  \- org.wildfly.common:wildfly-common:jar:1.7.0.Final-redhat-00003:compile
      [INFO] +- org.eclipse.parsson:parsson:jar:1.1.7.redhat-00002:compile
      [INFO] |  \- jakarta.json:jakarta.json-api:jar:2.1.3.redhat-00002:compile
      [INFO] +- org.junit.jupiter:junit-jupiter-engine:jar:5.10.3:test
      [INFO] |  +- org.junit.platform:junit-platform-engine:jar:1.10.3:test
      [INFO] |  |  +- org.opentest4j:opentest4j:jar:1.3.0:test
      [INFO] |  |  \- org.junit.platform:junit-platform-commons:jar:1.10.3:test
      [INFO] |  +- org.junit.jupiter:junit-jupiter-api:jar:5.10.3:test
      [INFO] |  \- org.apiguardian:apiguardian-api:jar:1.1.2:test
      [INFO] \- io.quarkus:quarkus-bom:pom:3.15.1.redhat-00003:test
      

      So Maven resolution all results in stuff managed by platform, while jbang does not.

              manderse@redhat.com Max Andersen
              mjurc@redhat.com Michal Jurc
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: