anchor.diff:  
   Due to the limited usage of OSGi and the maintenance burden it brings, the OptaPlanner jars in the 8.x series no longer include OSGi metadata in their `META-INF/MANIFEST.MF` file.
   
  -[.upgrade-recipe-minor]
  +[.upgrade-recipe-minor.upgrade-recipe-public-api]
   === `filterClassList` replaced by a single filterClass
   
   The configuration of `EntitySelector`, `ValueSelector` and `MoveSelector` now has a single filter class in both the configuration API and the solver configuration XML.
  
positive.code:     }
  ----
  
  [.upgrade-recipe-minor]
  === `<valueSelector>`: `variableName` is now an attribute
  
  When power tweaking move selectors, such as `<changeMoveSelector>`, in a use case with multiple planning variables, the `<variableName>` XML element has been replaced by a `variableName="..."` XML attribute.
  
negative.code:   <valueSelector variableName="room"/>
  ----
  
  [.upgrade-recipe-minor.upgrade-recipe-public-api]
  === Partitioned Search: `threadFactoryClass` removed
  
  Now that `<solver>` has supported a `<threadFactoryClass>` element for a while, the `<threadFactoryClass>` element under `<partitionedSearch>` has been removed.
  