Uploaded image for project: 'Red Hat Build of Apache Camel for Quarkus'
  1. Red Hat Build of Apache Camel for Quarkus
  2. CEQ-1672

camel-dependencies POM properties are not in sync with camel-parent

XMLWordPrintable

    • False
    • False
    • 0

      The productized Camel builds coming out of PNC don't seem to have the version properties in camel-parent/pom.xml in sync with camel-dependencies/pom.xml.

      There's a Maven plugin that should do the alignment:

      https://github.com/jboss-fuse/camel/blob/camel-3.11.1-branch/catalog/camel-catalog/pom.xml#L164-L181

      To see this, compare the snakeyaml-version property.

      camel-parent

      curl -L http://indy.psi.redhat.com/api/content/maven/hosted/pnc-builds/org/apache/camel/camel-parent/3.11.1.fuse-800012-redhat-00001/camel-parent-3.11.1.fuse-800012-redhat-00001.pom -s | grep "<snakeyaml-version>"
    <snakeyaml-version>1.29.0.redhat-00001</snakeyaml-version>

      camel-dependencies

      curl -L http://indy.psi.redhat.com/api/content/maven/hosted/pnc-builds/org/apache/camel/camel-dependencies/3.11.1.fuse-800012-redhat-00001/camel-dependencies-3.11.1.fuse-800012-redhat-00001.pom -s |  grep "<snakeyaml-version>"
    <snakeyaml-version>1.29</snakeyaml-version>

      camel-dependencies is the parent POM for camel-quarkus. So this likely explains why some versions are not aligned properly between the two projects.

          1.
          		 Documentation Sub-task Closed Undefined Unassigned
          2.
          		 Productization Sub-task Closed Undefined Unassigned
          3.
          		 Review Test Sub-task Closed Undefined Unassigned
          4.
          		 Development Sub-task Closed Undefined Unassigned

              tcunning@redhat.com Thomas Cunningham
              jnethert@redhat.com James Netherton
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: