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

Remove Files.write from generators

    XMLWordPrintable

Details

    • Task
    • Resolution: Done
    • Major
    • None
    • None
    • None
    • None

    Description

      There are multiple Files.write directly inside the generators while this should be delegated to the external container (KogitoAssetsProcessor or kogito-maven-plugin.
      The goal of this ticket is:

      • Remove all Files.write from inside the generator
      • Remove param Collection<GeneratedFile> and make methods always return a new collection of generate files (to avoid the side effect)
      • Remove all imageMetadata (and label) code because it use Files.write and it is no more used by the operator so it is better to remove the whole feature

      Attachments

        Issue Links

          blocks

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. KOGITO-3072 Restructure codegen (part 2)

          • 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
          causes

          Bug - A problem that impairs or prevents the functions of the product. KOGITO-4115 Due to removal of `target/classes/persistence` path, S2I tests of images are failing with persistence enabled

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed
          is related to

          Bug - A problem that impairs or prevents the functions of the product. KOGITO-4517 Update code base and documentation after proto files generation refactoring

          • 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

          Activity

            People

              dzonca@redhat.com Daniele Zonca
              dzonca@redhat.com Daniele Zonca
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: