In 5.4.0.CR1, to not have the exception, I put
ValueRange.excludeUninitializedPlanningEntity on false (That also works if
I dont use this attribute, its default value is false). The solver seems
doing the right moves.
--
View this message in context:
http://drools.46999.n3.nabble.com/Drools-Planner-multiple-planning-entiti...
Sent from the Drools: User forum mailing list archive at
Nabble.com.