Issue #234: Using builtin annotation classes before creating a CAS can break type system management

[reckart]

What's in the PR

• Try fixing the case if a JCCI was created with a bad type ID because the type ID had not been set yet

How to test manually

• Try running the ClearTK TimeMlAnnotateTest caugh

Automatic testing

• PR adds/updates unit tests

Documentation

• PR adds/updates documentation

Organizational

• PR adds/updates dependencies.
  _{^{Only dependencies under approved licenses are allowed. LICENSE and NOTICE files in the respective modules where dependencies have been added as well as in the project root have been updated.}}

[azazali30]

@reckart are we merging this fix, we are waiting for this fix to merge so that we can proceed with refactoring/442-Upgrade-to-UIMAv3

[reckart]

There is no fix yet - I need to find time to investigate it further because changes in this PR do not yet resolve the problem.

The alternative would be a workaround. I think it might be sufficient to create a dummy CAS before the failing tests accesses the JCas classes.

[reckart]

The work in this branch so far is unable to fix the problem.

The recommended workaround is to create a CAS object before working with any JCas classes.