The "research" reveals: 1) the DocumentAnnotation Jar is the JCas cover classes for the "base" (no extra features merged) version of this CAS Type.
2) It is not explicitly included into the runtime build 3) It comes in as a Jar, and also into the classpath, because it is a dependency of uimaj-tools, which is explicitly listed as a dependency, and uimaj-tools has a transitive dependency on the JCas cover classes. 4) The uimaj-tools dependency on the JCas cover classes is only in one spot - where the FileSystemCollectionReader class uses it to set the "language" into the CAS. 5) This is easily avoided - since there's a CAS and JCas method to set the document language; this method uses the non-JCas interface to the CAS to set this feature. I'll update the FileSystemCollectionReader (we actually have two versions of this same class - one had already been updated) to do this, and then I suspect the uimaj-ep-runtime will no longer have this transitive dependency, and will no longer include this jar. -Marshall On 7/26/2013 11:45 AM, Marshall Schor wrote: > On 7/26/2013 11:25 AM, Peter Klügl wrote: >> On 26.07.2013 17:16, Marshall Schor wrote: >>> See https://issues.apache.org/jira/browse/UIMA-1027 >> Ah ok, that was before my time :-) I gonna take a look at the issue. >> >> The implementation of the type was included in o.a.u.runtime-2.4.0. I >> have a somewhat internal type that extends that class and now its parent >> class is gone. Interestingly enough, there are no problems if I start a >> new vm when launching a Ruta script, because the classpath collector >> adds the uimaj-document-annotation-2.4.1.jar, which it found in the bundle. >> >>> I think if your plugin needs this, it needs to provide it - would that work? >> I could provide it, but I am actually removing the dependencies and the >> inheritance right now. I see no need to rely on that class. >> >> Maybe the jar should be removed from the runtime plugin sometime in future? > Interesting... This is coming into the build in the step which copies > "dependencies". It's not, itself, listed as a dependency, but it comes in via > being a transitive dependency in uimaj-tools. > > Have to do a bit more research to figure this out... > > -Marshall >> Best, >> >> Peter >> >> >>> -Marshall >>> >>> On 7/26/2013 11:06 AM, Marshall Schor wrote: >>>> Thanks, Peter. >>>> >>>> If I recall, this ommission was intentional; I'll try and find the history >>>> behind this. I think it had to do with the fact that the Document >>>> Annotation >>>> class is a JCas cover class for the UIMA document annotation Type. And >>>> due to >>>> the fact (and common practice) that people "extend" UIMA types with >>>> additional >>>> features, to enable this, it was thought that the user would provide their >>>> (potentially) custom version of the Document Annotation class, and that >>>> having >>>> the "base" version of this JCas type in the runtime would prevent this. >>>> >>>> -Marshall >>>> >>>> On 7/26/2013 10:55 AM, Peter Klügl wrote: >>>>> I know the vote is already closed, but I wanted to mention something >>>>> anyway: >>>>> >>>>> the runtime plugin contains six jars, but the manifest lists only five >>>>> of them as embedded and as the additional classpath. >>>>> uimaj-document-annotation-2.4.1.jar is missing and this is prevents >>>>> other plugins to actually use the jcas class DocumentAnnotation. >>>>> >>>>> Best, >>>>> >>>>> Peter >>>>> >>>>> >>>>> >>>>> >>>>> On 26.07.2013 16:44, Marshall Schor wrote: >>>>>> I try mvn deploy -Papache-release >>>>>> >>>>>> to emulate what the release process did :-)... >>>>>> >>>>>> -Marshall >>>>>> On 7/26/2013 10:11 AM, Richard Eckart de Castilho wrote: >>>>>>> Hum. I guess you can check out the 2.4.1 rc4 tag from SVN and just run >>>>>>> "mvn deploy" to stage it again, no? >>>>>>> >>>>>>> -- Richard >>>>>>> >>>>>>> Am 26.07.2013 um 16:06 schrieb Marshall Schor <m...@schor.com>: >>>>>>> >>>>>>>> Well, not enough coffee... >>>>>>>> >>>>>>>> There were 2 things in the "staging repository" - I saw the dates, and >>>>>>>> thought, >>>>>>>> hmmm, I thought I had already dropped the older one... but maybe I'm >>>>>>>> mistaken, >>>>>>>> so I dropped it. >>>>>>>> >>>>>>>> The new one - well it turned out it wasn't "uima". >>>>>>>> >>>>>>>> So, I have accidentally dropped the staged RC4 candidate on the >>>>>>>> staging Nexus >>>>>>>> repository at repository.apache.org. I'm asking on the repository >>>>>>>> mailing list >>>>>>>> if there's any recovery for this (short of re-doing the release >>>>>>>> candidate...). >>>>>>>> >>>>>>>> If not, I apologize for this error, but will need to redo this >>>>>>>> release... >>>>>>>> >>>>>>>> -Marshall >
