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

PMML API dependency fails to resolve path when in Quarkus mutable-jar context

    XMLWordPrintable

Details

    • False
    • None
    • False
    • Hide

      Exclude the mentioned dependencies from the SW project.

      Show
      Exclude the mentioned dependencies from the SW project.
    • Hide

      Build a SW application with the quarkus CLI as:

      quarkus build -Dquarkus.package.type=mutable-jar

      Then run:

      export QUARKUS_LAUNCH_DEVMODE=true; java -jar -Dquarkus.kogito.devservices.enabled=false target/quarkus-app/quarkus-run.jar

      Apart from the Data Index error if devservices is enabled, you should see the error reported in this issue.

      Show
      Build a SW application with the quarkus CLI as: quarkus build -Dquarkus. package .type=mutable-jar Then run: export QUARKUS_LAUNCH_DEVMODE= true ; java -jar -Dquarkus.kogito.devservices.enabled= false target/quarkus-app/quarkus-run.jar Apart from the Data Index error if devservices is enabled, you should see the error reported in this issue.
    • ---
    • ---
    • Critical

    Description

      See KOGITO-8183 comments for context.

      What happens is that the kogito-api depends on kogito-pmml-api-dependencies. This dependency, for some reason, is defining its path to an empty string in the classloader. See:

      org.kie.kogito:kogito-pmml-api-dependencies::jar:2.0.0-SNAPSHOT[paths: ]

      The same reproducer defined in KOGITO-8183 applies here as well. Copying for the sake of documenting the issue.

      It might be necessary to open an issue on Drools side as well. cc mfusco@redhat.com

      Attachments

        Issue Links

          blocks

          Bug - A problem that impairs or prevents the functions of the product. KOGITO-8183 Quarkus remote dev mode mutable jar startUp failed

          • 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.
          • Resolved

          Task - Represents a small unit of work that is not end-user facing. KOGITO-8296 [SPIKE] Enable Quarkus Dev/Augmentation mode in the running workflow instance

          • 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
          is related to

          Bug - A problem that impairs or prevents the functions of the product. KOGITO-8444 Kogito Codegen don't handle POM dependencies accordingly

          • 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.
          • Resolved

          Activity

            People

              gcardosi Gabriele Cardosi (Inactive)
              rhn-support-zanini Ricardo Zanini Fernandes
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: