uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marshall Schor (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 15:43:55 GMT

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

Marshall Schor commented on UIMA-1027:

Hi Mikhail,

Thanks for reporting that the class in org.apache.uima.jcas.tcas, DocumentAnnotation, is "missing".
 The jars in the UIMA runtime plugin are not supposed to have any references to this class,
so the fact that it is missing should not affect anything.  

However, when I scanned the code, I found one reference to this class, which is a bug, which
I'll fix under this Jira issue.  It is referred to in this line in the tools project, in the
FileSystemCollectionReader class:

((DocumentAnnotation) jcas.getDocumentAnnotationFs()).setLanguage(mLanguage);

The fix is to replace this with:


Is this the only issue you see, or are there others?  

> 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
> 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.

View raw message