[UIMA-165] Need JCAS fixes for DocumentatAnnotation and type merging

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.1
• Component/s: Core Java Framework
• Assignee: Adam P. Lally
• Reporter: Adam P. Lally
• Created: 08/Jan/07 18:48
• Updated: 18/Jan/07 18:10
• Resolved: 11/Jan/07 21:39

Description

The current build has the DocumentAnnotation JCas cover class in uima-core.jar. This creates a problem for anyone who has added features to this type and run JCasGen.

Fixes as suggested by Marshall and agreed by Adam:
> a) Do the work to make it easy to get singletons (or whatever we're
> calling this feature) out of the CAS
>
> b) Change JCasGen to not generate DocumentAnnotation if the merged
> version = the base
>
> c) Add the DocumentAnnotation jar back to the build, with instructions
> to remove it from the
> deployment and substitute a JCasGenerated one if the application needs a
> special one.

Sub-Tasks

• Change JCasGen to not generate DocumentAnnotation if the merged version = the base: Closed
• Create separate uima-document-annotation Maven project and jar file: Closed
• Update documentation for the use of JCAS with DocumentAnnotation: Closed