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

8.0 backwards incompatible changes for next major version

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Major Major
    • 8.0.0.Beta1
    • None
    • None
    • None
    • 8.0 backwards incompatible changes
    • Done
    • NEW
    • NEW

      For 9.0 look at https://issues.redhat.com/browse/PLANNER-2295

      It's a few years before we'll get to 8.0, but we need to start gathering these now as 7.0 is going into CR1.
       
      Radovan' list:

      • ValueSelectorConfig.variableName should no longer work as a nested element too. (PLANNER-2026)
      • Rename AcceptorConfig to LocalSearchAcceptorConfig (similarly for deciders, foragers)... (PLANNER-2027)
         

      Unassigned list:

      • Ideally, for 8.0 (or 9.0) we remove all non-getter/setters of the config classes while we internalize the SolverConfig in the SolverFactory. (maybe Radovan)

      Things to consider:

      • directory name != artifactId to avoid windows path 260 issue and to have quarkus/spring a submodule of integration
      • Rename <scoreDirectorFactory> to <scoring>?
      • Rename ScoreManager to SolutionManager to accomodate retriggerAllVariableListeners() too? (Are we giving the users a way to shoot them in the foot? Can we not just retrigger them every time? It's an ugly duckling: retriggerAllVariableListeners(), calculateScore(), getIndictmentMap(), ...)

            lpetrovi@redhat.com Lukáš Petrovický (Inactive)
            gdesmet@redhat.com Geoffrey De Smet (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: