Package and Description |
---|
org.optaplanner.core.api.domain.solution.drools |
org.optaplanner.core.api.score.buildin.hardsoftdouble |
org.optaplanner.core.api.score.buildin.simpledouble |
Interface and Description |
---|
org.optaplanner.core.api.score.FeasibilityScore
Moved
FeasibilityScore.isFeasible() up to Score . |
org.optaplanner.core.api.domain.entity.PlanningEntity.NullMovableEntitySelectionFilter |
org.optaplanner.core.api.domain.variable.PlanningVariable.NullReinitializeVariableEntityFilter |
org.optaplanner.core.api.domain.solution.Solution
Use
PlanningScore , ProblemFactCollectionProperty and ProblemFactProperty instead. Will be
removed in 8.0. |
Class and Description |
---|
org.optaplanner.core.api.score.holder.AbstractScoreHolder
for removal from public API
|
org.optaplanner.core.api.score.holder.AbstractScoreHolder.ConstraintActivationUnMatchListener
for removal from public API
|
org.optaplanner.core.impl.domain.solution.AbstractSolution
Use
PlanningSolution.autoDiscoverMemberType() instead. |
org.optaplanner.core.api.score.constraint.ConstraintMatchScoreComparator
If you need this, it is trivial to implement via
Comparator.comparing(Function) . |
org.optaplanner.core.api.score.constraint.ConstraintMatchTotalScoreComparator
If you need this, it is trivial to implement via
Comparator.comparing(Function) . |
org.optaplanner.core.api.score.buildin.hardsoftdouble.HardSoftDoubleScore
Double-based scores are deprecated as floating point numbers are not associative (A + B + C == C + B + A)
and therefore they are not compatible with incremental score calculation.
Use
HardSoftBigDecimalScore or a scaled HardSoftLongScore instead. |
org.optaplanner.core.impl.score.buildin.hardsoftdouble.HardSoftDoubleScoreDefinition
Double-based scores are deprecated as floating point numbers are not associative (A + B + C == C + B + A)
and therefore they are not compatible with incremental score calculation.
|
org.optaplanner.core.api.score.buildin.hardsoftdouble.HardSoftDoubleScoreHolder
Double-based scores are deprecated as floating point numbers are not associative (A + B + C == C + B + A)
and therefore they are not compatible with incremental score calculation.
Use
HardSoftBigDecimalScoreHolder or a scaled HardSoftLongScoreHolder instead. |
org.optaplanner.core.api.score.constraint.IndictmentScoreComparator
If you need this, it is trivial to implement via
Comparator.comparing(Function) . |
org.optaplanner.core.api.score.constraint.IndictmentScoreTotalComparator
If you need this, it is trivial to implement via
Comparator.comparing(Function) . |
org.optaplanner.core.api.score.comparator.NaturalScoreComparator
If you need this, it is trivial to implement via
Comparator.comparing(Function) . |
org.optaplanner.core.config.domain.ReflectionsKieVfsUrlType
for removal
|
org.optaplanner.core.config.domain.ReflectionsWorkaroundClasspathHelper
in favor of Quarkus extension or Spring Boot starter.
|
org.optaplanner.core.config.domain.ScanAnnotatedClassesConfig
in favor of the Quarkus extension or Spring Boot starter which handle annotation scanning more
efficiently.
|
org.optaplanner.core.api.score.buildin.simpledouble.SimpleDoubleScore
Double-based scores are deprecated as floating point numbers are not associative (A + B + C == C + B + A)
and therefore they are not compatible with incremental score calculation.
Use
SimpleBigDecimalScore or a scaled SimpleLongScore instead. |
org.optaplanner.core.impl.score.buildin.simpledouble.SimpleDoubleScoreDefinition
Double-based scores are deprecated as floating point numbers are not associative (A + B + C == C + B + A)
and therefore they are not compatible with incremental score calculation.
|
org.optaplanner.core.api.score.buildin.simpledouble.SimpleDoubleScoreHolder
Double-based scores are deprecated as floating point numbers are not associative (A + B + C == C + B + A)
and therefore they are not compatible with incremental score calculation.
Use
SimpleBigDecimalScoreHolder or a scaled SimpleLongScoreHolder instead. |
org.optaplanner.core.impl.localsearch.decider.acceptor.tabu.SolutionTabuAcceptor |
Annotation Type and Description |
---|
org.optaplanner.core.api.domain.solution.drools.ProblemFactCollectionProperty
In favor of
ProblemFactCollectionProperty . |
org.optaplanner.core.api.domain.solution.drools.ProblemFactProperty
In favor of
ProblemFactProperty . |
Constructor and Description |
---|
org.optaplanner.core.impl.score.director.drools.DroolsScoreDirectorFactory(SolutionDescriptor<Solution_>, KieBase)
for removal, legacy code.
|
org.optaplanner.core.impl.score.director.drools.testgen.TestGenDroolsScoreDirectorFactory(SolutionDescriptor<Solution_>, KieBase, List<String>, List<File>)
for removal, legacy code.
|
Enum Constant and Description |
---|
org.optaplanner.core.config.solver.EnvironmentMode.PRODUCTION
Use
EnvironmentMode.NON_REPRODUCIBLE instead. Will be removed in 8.0. |
org.optaplanner.core.config.localsearch.decider.acceptor.AcceptorType.SOLUTION_TABU
for removal.
|
Annotation Type Element and Description |
---|
org.optaplanner.core.api.domain.entity.PlanningEntity.movableEntitySelectionFilter
in favor of
PlanningEntity.pinningFilter() . |
org.optaplanner.core.api.domain.variable.PlanningVariable.reinitializeVariableEntityFilter
for removal. Instead, filter the entity selector of the placer in the construction heuristic.
|
Copyright © 2006–2020 JBoss by Red Hat. All rights reserved.