Hi Mikhail,
We appreciate your input - I find the OSGi stuff complex. I've
attempted to reply to your concerns below, but please respond if I'm not
understanding, or have perhaps misunderstood some detail about how OSGi
/ Eclipse is supposed to work :-)
Mikhail Sogrin (JIRA) wrote:
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.
Yes. This was done due to the discussion on this thread:
http://www.mail-archive.com/[email protected]/msg06246.html.
It seemed to be necessary. Is this causing a problem for you?
But contents of uima-document-annotator.jar were not added to 2.2.2 plugin.
This jar has the JCas cover class for the UIMA DocumentAnnotation type.
But we don't include this in the plugin so that applications which
extend the DocumentAnnotation type with additional UIMA 'features' can
generate a different JCas cover class for the DocumentAnnotation type
and substitute their own version of this class. For the background
discussion on this, see
http://incubator.apache.org/uima/downloads/releaseDocs/2.2.2-incubating/docs/html/references/references.html#ugr.ref.jcas.documentannotation_issues
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.
At the end of comments for UIMA-400 is the point about
uimaj-jcas-builtin-types.jar (which previously held the
DocumentAnnotation JCas cover class) is listed in the manifest, but not
present in the plugin. The comment there says it is fixed under
UIMA-549. But that fix didn't add the jar - rather the manifest entry
for uimaj-jcas-builtin-types.jar was removed.
Can you add your own version of the JCas cover types for
DocumentAnnotation in your particular use case?
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.
I'm not sure this is an error - isn't it common for a bundle to both
export and import a package? Section 3.5.6 of the OSGi r4.core
documentation says it's quite common for bundles to both import and
export the same package. Is this causing some particular trouble for you?
Thanks. -Marshall
