The issue arose from using the Maven Assembly Plugin to naively build an
executable jar with uimaFit components. Files supplied by different
dependencies overwrote each other during packaging and some types could not be
detected at runtime. The uimaFit documentation has this issue recorded in
Hi Marshall,
I work with Andrew. Thanks for the reply, this definitely helps!
Best regards,
J.K. Accetta
On 8/23/17 8:50 AM, Marshall Schor wrote:
Hi,
Those two listing of the type system appear to show that the *working* version
does not have cTakes, and the *failing* version has cTakes.
Hi,
Those two listing of the type system appear to show that the *working* version
does not have cTakes, and the *failing* version has cTakes.
Any ideas why this might be so?
The stack trace appears to show that the "FileSystemCollectionReader" class is
running the getNext method, and that is
I am working with UIMA-Alpha02 and am currently trying to build a jar to make a
standalone application. (not pear because we want our users to have just the
JDK and not require ecilpse or UIMA) In many cases we use maven to build and
package the jar and it runs fine. Other times the jar is
