On Fri, 27 May 2011 02:15:37 -0700, Thilo Götz twgo...@gmx.de wrote:
It is also worth pointing out that if you control the code, you
can write/package your annotators so they just run out of a jar
file. The resource loading mechanism of UIMA can load resources
from the classpath, i.e., from a
On 05/26/2011 08:37 PM, Greg Holmberg wrote:
[...] What I want may simply be outside the design target of PEAR files. My
expectations of PEAR files were based on how other archive formats in
Java work. JAR files, WAR files, etc. These can all be use in-place,
without any re-writing of their
On 27/05/11 09:57, Jens Grivolla wrote:
On 05/26/2011 08:37 PM, Greg Holmberg wrote:
[...] What I want may simply be outside the design target of PEAR files. My
expectations of PEAR files were based on how other archive formats in
Java work. JAR files, WAR files, etc. These can all be use
Hi Marshall--
To support something like this, I'm thinking it would require that during
initialization of the pipeline, UIMA would need to install the PEAR in
some
temporary location somewhere, and then use that installation. (The
installation
is needed because of the possibility that
Hi UIMA users--
I'm converting all my annotators to PEAR packaging. I like having
everything in one file, especially when there are many additional files
that are part of the annotator--resources, config, data, etc. It just
makes it a lot easier to consume the annotator.
using the PEAR packaging maven plug-in. This works fine, but I was
surprised when the PEAR file didn't get installed (i.e. it didn't show up
under ~/.m2/repository). It seems like a reasonable expectation--you
build a jar artifact, it gets installed/deployed; you build a PEAR
artifact
