Uploaded image for project: 'Drools'
  1. Drools
  2. DROOLS-6643

KieModuleMarshaller initializes java.awt classes at build time via xstream which breaks Quarkus native compilation

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • None
    • 7.59.0.Final
    • core engine
    • None
    • 2021 Week 43-45 (from Oct 25)
    • NEW
    • NEW

    Description

      Since Quarkus changed java.awt classes to be run-time initialized, OptaPlanner native compilation started failing as the KieModuleMarshaller is initialized at build time and depends on java.awt classes through XStream (see the attached stacktrace).

      There is already a workaround in place that changes the KieModuleMarshaller initialization to the run time (https://github.com/kiegroup/optaplanner/pull/1594), yet this issue should be better fixed closer to its source.

      Please see https://github.com/quarkusio/quarkus/issues/20491 for more details.

      Attachments

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. KOGITO-6228 dmn-pmml-quarkus-example does not compile in native mode

          • 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

          Bug - A problem that impairs or prevents the functions of the product. FAI-668 Explainability: Native build is broken

          • 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

          Task - Represents a small unit of work that is not end-user facing. PLANNER-2584 Clean up after DROOLS-6643

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Resolved

          Activity

            People

              mfusco@redhat.com Mario Fusco
              rsynek@redhat.com Radovan Synek
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: