uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mikhail Sogrin (JIRA)" <uima-...@incubator.apache.org>
Subject [jira] Commented: (UIMA-1027) Classes from uima-document-annotator.jar are not in Eclipse plugin
Date Wed, 14 May 2008 19:02:55 GMT

    [ https://issues.apache.org/jira/browse/UIMA-1027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12596902#action_12596902
] 

Mikhail Sogrin commented on UIMA-1027:
--------------------------------------

Thank you for answers.

I use a typesystem stored in a separate XML file, and import it by name in annotator descriptors.
When I click on JCasGen in typesystem descriptor, annotation classes are generated, but they
extend DocumentAnnotation class, which Eclipse immediately marks as undefined. 

Ok, now I've found a notice in UIMA reference that it's not recommended to extend DocumentAnnotation,
however, typesystem editor did not show any such notice and DocumentAnnotation seemed like
a proper super type for document-wide annotation. I've changed super type to simple Annotation
now, so the problem is fixed for me.

> Classes from uima-document-annotator.jar are not in Eclipse plugin
> ------------------------------------------------------------------
>
>                 Key: UIMA-1027
>                 URL: https://issues.apache.org/jira/browse/UIMA-1027
>             Project: UIMA
>          Issue Type: Bug
>          Components: Eclipse plugins
>    Affects Versions: 2.2.2AS, 2.2.2S
>            Reporter: Mikhail Sogrin
>
> Eclipse plugin org.apache.uima.runtime previously contained jars inside a plugin. Version
2.2.2 has jars unzipped. But contents of uima-document-annotator.jar were not added to 2.2.2
plugin.
> I've previously submitted a report (UIMA-400) about the same jar which was not added
to 2.1.0 plugin by mistake, and it was fixed in 2.2.0, and now broken again in 2.2.2.
> In addition, there's a circular dependency for the package org.apache.uima.jcas.tcas,
i.e. the same package is exported and imported in manifest. Probably, it's caused by the same
missing classes from that jar.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message