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

Introduce ConstraintOccurrenceTotal and make it easier to extend the ConstraintType and don't split up positive and negative hard constraints types

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Done
    • Icon: Major Major
    • 6.0.0.Beta1
    • None
    • optaplanner-core
    • None

      • ConstraintType is now an enum and so it's annoying to add VERY_SOFT etc (you can't reuse the ConstraintOccurrence implementations).
      • ConstraintType should not make a difference between positive and negative hard constraints
      • ConstraintOccurrenceTotal should give domain and api support to understand and enumerate the total of the rules.

      Think about:

      • new IntConstraintOccurrenceTotal(int level, String ruleId, boolean positiveOrNegative)
      • myIntConstraintOccurrenceTotal.createOcccurence(weight, causes)
      • LevelBasedScore (instead of HardAndSoftScore?)

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

                Created:
                Updated:
                Resolved: