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 10:31:55 GMT

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

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

The main problem here is that classes org.apache.uima.jcas.tcas.DocumentAnnotation and DocumentAnnotation_Type,
which are in uima-document-annotation.jar in lib/ are not present in org.apache.uima.runtime
plugin, instead there's Import-Package for it. However, these classes are not present anywhere
in Eclipse plugins and therefore this import will never be resolved.

If these classes were present in runtime plugin (as they were in 2.2.0 and 2.2.1), importing
package would have been unnecessary and there would be no problem with wiring.

> 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