[UIMA-6017] uv3 make cascompare more useful by eliminating duplicate reporting

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 3.0.1SDK
• Fix Version/s: 3.0.2SDK
• Component/s: Core Java Framework, Tools
• Assignee: Unassigned
• Reporter: Marshall Schor
• Created: 29/Mar/19 17:50
• Updated: 29/Mar/19 18:05
• Resolved: 29/Mar/19 18:05

Description

When using the cas compare to discover the root cause of two CASs miscomparing, it is helpful to exclude showing miscompares that are caused by already reported miscompares. 

For example, if you have some collection of Feature Structures, and one of them miscompares and you report that, it is helpful to not also report the two collections are miscomparing.  

If you don't exclude these "upper level" miscompares from reporting, there are typically so many reported miscompares, that it's hard to focus on the root cause.

Also, remove code that was conditionally sorting some collections during compare - this broke other code and isn't needed - any sorting should be done before this routine is called.