Bug 1077542

I took the content of the staged BRMS 6 planner guide:
  http://documentation-devel.engineering.redhat.com/site/documentation/en-US/Red_Hat_JBoss_BRMS/6.0/html-single/Business_Resource_Planner_Guide/index.html

and also the content of the community 6.0.1 guide released a few months ago:
  http://docs.jboss.org/drools/release/6.0.1.Final/optaplanner-docs/html_single/index.html

I copy pasted the content of both in a file and then used meld to compare both, while ignoring white space (which is an option in meld's UI).

The BRMS 6 planner is full of bugs. Some examples:

- Description of the problem
BRMS 6 guide (incorrect)
=>
OptaPlanner community guide (correct)


- Usage of invalid API's THAT DO NOT COMPILE:
    @ValueRange(type = ValueRangeType.FROM_SOLUTION_PROPERTY, solutionProperty = rowList")
    public Row getRow() {
=>
    @PlanningVariable(valueRangeProviderRefs = {"rowRange"})

- Usage of namespace org.drools.planner:
<planningEntityClass>org.drools.planner.examples.nqueens.domain.Queen</planningEntityClass>
=>
<planningEntityClass>org.optaplanner.examples.nqueens.domain.Queen</planningEntityClass>

- Incomplete sentences:
That Collection must not contain the value null, even for a .
=>
That Collection must not contain the value null, even for a nullable planning variable.

- Missing links causing incomplete sentences:
See for more information.
=>
See sorted selection for more information.

- All (or almost all) internal links in the document are broken:
info: Log every phase and the solver itself. See .
=>
info: Log every phase and the solver itself. See scope overview.

- Invalid interface/API listings:
    void beforeAllVariablesChanged(Object entity);
=>
    void beforeVariableChanged(Object entity, String variableName);

- Stale project names:
Store and release in the Guvnor repository 
=>
Store and release in the KIE Workbench repository

- Use of deprecated, slow API's:
        insertLogical(new UnweightedConstraintOccurrence("multipleQueensHorizontal", $q1, $q2));
=>
        scoreHolder.addConstraintMatch(kcontext, -1);



This is just the tip of the iceberg. Use the meld procedure described above to find them all.