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

(Pillar)SwapMoveSelectorConfig: Wrap <variableNameInclude> in <variableNameIncludes> (8.0)

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Done
    • Optional
    • Future
    • None
    • optaplanner-core
    • None

    Description

      Motivation: make the configs for move selectors more consistent.

      Use

          @XStreamAlias("variableNameIncludes")
    @XStreamConverter(value = NamedCollectionConverter.class,
            strings = {"variableNameInclude"}, types = {String.class}, useImplicitType = false)
    private List<String> variableNameIncludeList = null;

      to get

      <variableNameIncludes>
  <variableNameInclude>period</variableNameInclude>
  <variableNameInclude>room</variableNameInclude>
</variableNameIncludes>

      This is a backwards incompatible change, so wait (a few years?) until 8.0 at least.

      Attachments

        Issue Links

          is incorporated by

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. PLANNER-750 8.0 backwards incompatible changes for next major version

          • 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

          Activity

            People

              rsynek@redhat.com Radovan Synek
              gdesmet@redhat.com Geoffrey De Smet (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: