[
https://issues.apache.org/jira/browse/UIMA-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Lally resolved UIMA-170.
-----------------------------
Resolution: Fixed
Assignee: Marshall Schor (was: Adam Lally)
Marshall, please review my documentation changes. I reworte the JCAS Reference
chapter to more completely explain the issues involving using JCAS with
type-merging, including issues specific to DocumentAnnotation. In several
other chapters I added <warning> sections that link to this JCAS Reference
chapter. My updates assume that JCasGen and CDE will be generating warning
messages when type-merging is used.
> Update documentation for the use of JCAS with DocumentAnnotation
> ----------------------------------------------------------------
>
> Key: UIMA-170
> URL: https://issues.apache.org/jira/browse/UIMA-170
> Project: UIMA
> Issue Type: Sub-task
> Components: Documentation
> Reporter: Adam Lally
> Assigned To: Marshall Schor
> Fix For: 2.1
>
>
> Documentation should explain that if the user adds features to
> DocumentAnnotation then they should omit uima-document-annotation.jar from
> their classpath and use their own generated class instead.
> The documentation should explain that using this feature will result in more
> work for people who are attempting to assemble annotators togther into
> aggregates, in particular that they may need to be willing and have the
> know-how to re-run JCasGen over the merged type system.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
