[UIMA-5974] uv3 unnecessary API change from v2 breaking binary compatibility

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0.1SDK
• Fix Version/s: 3.0.2SDK
• Component/s: Core Java Framework
• Assignee: Marshall Schor
• Reporter: Marshall Schor
• Created: 31/Jan/19 03:29
• Updated: 31/Jan/19 22:18
• Resolved: 31/Jan/19 22:18

Description

Uima v3 strives to be binary compatible with v2, with the exception of needing new JCas classes.  This allows a simpler migration because (the goal is) you don't need to recompile JARs - the same Jars can be used with either v2 or v3.

Found a few spots where v3 changed the signature of a public API, usually to a more specific type, which, while correct, breaks binary compatibility.  Reverse these changes.