Uploaded image for project: 'camunda BPM'
  1. camunda BPM
  2. CAM-11345

Remove BOM from platform parent hierarchy

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: L3 - Default L3 - Default
    • 7.13.0, 7.13.0-alpha2
    • None
    • engine
    • None

      The platform modules should not extend the BOM as that ties the versions of all camunda-* artifacts to the current snapshot. We have certain modules (qa rolling update, instance migration, ...) that use older Camunda versions. With the BOM as an inherited pom, we must declare all dependencies explicitly to use an older version (see for example https://github.com/camunda/camunda-bpm-platform/blob/7.12.0/qa/test-db-rolling-update/rolling-update-util/pom.xml#L23-L47). This is redundant and error-prone.

      In addition, this can create a dependency chain such as:

      A (7.13.0-SNASPHOT) depends on B (7.12.0) depends on C (7.13.0-SNAPSHOT)

      This messes up how the artifacts in the Maven reactor get resolved. I.e. artifact C would not be detected that it will be produced by the current reactor (and therefore must be built before artifact A). Impact: Older snapshots of C may be used in the build and parallel builds may fail (see CAM-11210).

        This is the controller panel for Smart Panels app

          1. example.zip
            4 kB

              yana.vasileva Yana Vasileva
              thorben.lindhauer Thorben Lindhauer
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: