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 20:41:55 GMT

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

Marshall Schor commented on UIMA-1027:
--------------------------------------

I'm thinking you may an issue not at all related to what we've been discussing here.

When you say "extend DocumentationAnnotation class" do you mean you defined a new UIMA Type,
and made its superType org.apache.uima.tcas.DocumentationAnnotation?

If so, then the fix you need has nothing at all to do with the Eclipse plugins, I think. 
Rather, in your Eclipse project, you just have to add to that project's build path the uima-document-annotation.jar
(found in %UIMA_HOME%\lib ).  

Please let us know if this is the issue, or if it was something else we are not understanding
yet...
-Marshall

> 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