Details

    • Type: Task
    • Status: Closed
    • Priority: L3 - Default
    • Resolution: Done
    • Affects Version/s: 7.12.0
    • Fix Version/s: 7.12.0, 7.12.0-alpha2
    • Component/s: dmn-engine, engine
    • Labels:
      None
    • Title Keywords:
      dmn engine, repository, merge

      Description

      AT:

      • DMN Engine repository is moved to platform
      • DMN Engine artifacts retain the same versioning as the platform
      • The Maven coordinates remain consistent with the platform

      Side notes:

      • Git history should be kept

        Issue Links

          Activity

          Hide
          leonhardt.wille Leonhardt Wille added a comment -

          Archived camunda-engine-dmn after cleaning up all settings (disabled/removed wikis, projects, outdated webhooks).

          Show
          leonhardt.wille Leonhardt Wille added a comment - Archived camunda-engine-dmn after cleaning up all settings (disabled/removed wikis, projects, outdated webhooks).
          Hide
          leonhardt.wille Leonhardt Wille added a comment -

          Can the repositories camunda-engine-dmn-maintenance and camunda-engine-dmn be archived?

          Show
          leonhardt.wille Leonhardt Wille added a comment - Can the repositories camunda-engine-dmn-maintenance and camunda-engine-dmn be archived?
          Hide
          nikola.koevski Nikola Koevski added a comment -

          For some reason, the commits aren't synced with the ticket.

          • On the platform, the commit with the changes is 2ed6667d
          • On camunda-engine-dmn, the updated readme is here: 2282a1ef
          Show
          nikola.koevski Nikola Koevski added a comment - For some reason, the commits aren't synced with the ticket. On the platform, the commit with the changes is 2ed6667d On camunda-engine-dmn, the updated readme is here: 2282a1ef
          Hide
          nikola.koevski Nikola Koevski added a comment - - edited

          Changes to the project:

          • The DMN BOM remains a child of release-parent since it causes a cyclic dependency if the parent is changed to the Camunda BOM.
          • The DMN root pom is now a child of camunda-database-settings. It doesn't inherit directly from camunda-parent since camunda-database-settings also contains the camunda.version.old property used in the DMN engine testing.
          • I removed the DMN dependencies that are already declared in parent.
          • Adjust the Apache Felix plugin so it's compatible with the platform.
          Show
          nikola.koevski Nikola Koevski added a comment - - edited Changes to the project: The DMN BOM remains a child of release-parent since it causes a cyclic dependency if the parent is changed to the Camunda BOM. The DMN root pom is now a child of camunda-database-settings. It doesn't inherit directly from camunda-parent since camunda-database-settings also contains the camunda.version.old property used in the DMN engine testing. I removed the DMN dependencies that are already declared in parent. Adjust the Apache Felix plugin so it's compatible with the platform.

            People

            • Assignee:
              Unassigned
              Reporter:
              nikola.koevski Nikola Koevski
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development