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

Quarkus: Extensions: Circular dependency on kogito-apps

    XMLWordPrintable

Details

    • Task
    • Resolution: Unresolved
    • Major
    • None
    • 1.15.0.Final
    • Core Engine, Data Index, Image
    • None
    • False
    • False

    Description

      We have two Quarkus extensions/addons that start kogito images.

      These images are produced by kogito-images based on modules in kogito-apps.

      Here's the data-index example; a similar one exists for tracing-addon:

      The processes extension also upon the publication of a kogito image to quay.io; that is not built until kogito-apps and not published to quay.io until kogito-images.

      This, in essence, means the kogito Quarkus extensions rely upon the last published quay.io image and hence are effectively "one version behind".

      Is there anything we can do about this!?

      Attachments

        Issue Links

          is related to

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. KOGITO-6684 Kogito images for supporting services should no longer download the runner jar from maven repository

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          Feature Request - Feature requests from customers and/or users KOGITO-5508 Add data index inmemory dev service to Kogito process extension

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. FAI-602 Integrate the AuditUI with the Quarkus DevUI

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Done

          Activity

            People

              cnicolai@redhat.com Cristiano Nicolai
              manstis@redhat.com Michael Anstis
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated: