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

Qpid : Unproductised dependencies of supported extension

XMLWordPrintable

    • False
    • None
    • False
    • +
    • Hide 
       mvn com.redhat.quarkus.platform:quarkus-maven-plugin:3.8.1.temporary-redhat-00008:create \
 -DprojectGroupId=my-groupId -DprojectArtifactId=app -DprojectVersion=1.0.0-SNAPSHOT -DpackageName=org.my.group \
 -DquarkusRegistryClient=false -DplatformArtifactId=quarkus-bom -DplatformGroupId=com.redhat.quarkus.platform \
 -DplatformVersion=3.8.1.temporary-redhat-00008 \
 -Dextensions=quarkus-smallrye-graphql,qpid-jms \
 -Dmaven.repo.local=$REPO

cd app

mvn clean dependency:tree -Dquarkus.package.output-name=quarkus -Dmaven.repo.local=$REPO > tree.txt

grep -v "redhat" tree.txt
      Show
      mvn com.redhat.quarkus.platform:quarkus-maven-plugin:3.8.1.temporary-redhat-00008:create \ -DprojectGroupId=my-groupId -DprojectArtifactId=app -DprojectVersion=1.0.0-SNAPSHOT -DpackageName=org.my.group \ -DquarkusRegistryClient=false -DplatformArtifactId=quarkus-bom -DplatformGroupId=com.redhat.quarkus.platform \ -DplatformVersion=3.8.1.temporary-redhat-00008 \ -Dextensions=quarkus-smallrye-graphql,qpid-jms \ -Dmaven.repo. local = $REPO cd app mvn clean dependency:tree -Dquarkus.package.output-name=quarkus -Dmaven.repo. local = $REPO > tree.txt grep -v "redhat" tree.txt
    • ---

      Application which uses supported qpid-jms extension transitively depends on the following non-productised dependencies In ER2:
      new ones (required by qpid-jms extension):
      org.amqphub.quarkus.quarkus-qpid-jms-2.6.0.jar
      org.apache.qpid.qpid-jms-client-2.5.0.jar
      jakarta.jms.jakarta.jms-api-3.1.0.jar

       

      This happened (and is expected to in initial ER builds) because no window was given between the core and platform productization builds for the extension to be productised against the new core. Once a permanent core build is productised that is expected to pass testing and be released, and a window is given prior to the platform build, the extension will be similarly productised with a permanent build against the new core and updated for the platform build.

      (This didnt show up in ER1 though since the 3.8.1 based ER1 platform build used the old productised 3.2.x participant extension versions. This was changed in the 3.8.2 based ER2 such that the current 3.8.x unproductised upstream participant versions were used as would be expected.)

              gemmellr Robbie Gemmell
              antcosta Antonio Costa
              Fedor Dudinskii Fedor Dudinskii
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: