Uploaded image for project: 'Kogito'
  1. Kogito
  2. KOGITO-5719

Transform all Kogito Add-Ons into Quarkus Extension

XMLWordPrintable

    • Icon: Enhancement Enhancement
    • Resolution: Done
    • Icon: Major Major
    • 1.12.0.Final
    • 1.9.1.Final
    • Core Engine
    • None
    • False
    • False
    • Documentation (Ref Guide, User Guide, etc.), Release Notes
    • undefined
    • 2021 Week 31-33 (from Aug 2), 2021 Week 34-36 (from Aug 23), 2021 Week 37-39 (from Sep 13)

      Our Add-Ons add capabilities on top of every Kogito project. Today, a user must add their dependencies manually into the POM. By transforming the Kogito Quarkus Add-Ons into real extensions, we can benefit with:

      1. Leverage Quarkus Maven Plugin "add-extension" capability.
      2. Leverage Quarkus code.io website.
      3. Clear separation of build time classpath when generating code. A must for KOGITO-5620.

      This won't change anything for end-users since the artifacts ids will still be the same as the pom files. However, internally and from a UX perspective, it will have huge impact thou.

              rhn-support-zanini Ricardo Zanini
              rhn-support-zanini Ricardo Zanini
              Marian Macik Marian Macik
              Marian Macik Marian Macik
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: