Uploaded image for project: 'OptaPlanner'
  1. OptaPlanner
  2. PLANNER-1771

Make Quarkus Optaplanner extension processor exit if no instances are found

    XMLWordPrintable

Details

    • Task
    • Resolution: Done
    • Major
    • 7.43.0.Final, 8.0.0.Beta1
    • None
    • None
    • None
    • 2020 Week 04-06 (from Jan 20), 2020 Week 34-36 (from Aug 17)
    • 5
    • NEW
    • NEW

    Description

      Link to behaviour spec discussion: https://github.com/quarkusio/quarkus/pull/5622#pullrequestreview-319793742

      Similar to Hibernate, the desired specs are:

      • If there is at least one @PlanningEntity class but not a @PlanningSolution, it should fail fast
      • If there is no @PlanningEntity class but there is a @PlanningSolution, it should fail fast
      • If there are neither, it shouldn't fail: it should simply skip whatever the optaplanner extension does next

      Attachments

        Issue Links

          relates to

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) PLANNER-2127 Switch default ClassLoader from *Config.getClass.getClassLoader() to Thread.currentThread().getContextClassLoader()

          • 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

              gdesmet@redhat.com Geoffrey De Smet (Inactive)
              jucui Julian Cui (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: