Thanks Richard for looking into this. As I mentioned in another message,
I recently updated ConceptMapper to get rid of deprecated stuff and make
it work with uimaFIT, and other addons would probably also need some
updates.
How do we go about this? In the case of ConceptMapper there's my patch
against the 2.3.1Addons version that fixes the bug, and then there's an
update to it to make it more in line with current UIMA practice.
So do we first fix the bug, then open a new issue to make it more
modern? Will there be new addon releases, or should we release updated
addons individually? It would probably not make sense to make a common
release of all addons where many of the components extend deprecated
classes such as TextAnnotator.
I don't care much about binary releases, but having official updated
maven artifacts would be nice at some point...
Bye,
Jens
On 10/24/2013 08:36 PM, Richard Eckart de Castilho (JIRA) wrote:
[
https://issues.apache.org/jira/browse/UIMA-2387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13804513#comment-13804513
]
Richard Eckart de Castilho commented on UIMA-2387:
--------------------------------------------------
Ok, I understand.
I tried checking out the add-ons to try out the patch, but apparently the
add-ons have had little attention for quite some time. At least, checking them
out in Eclipse gives me lots of errors and red projects. Doesn't look like this
is going to be a walk in the park...
ResultingAnnotationName not optional in ConceptMapper
-----------------------------------------------------
Key: UIMA-2387
URL: https://issues.apache.org/jira/browse/UIMA-2387
Project: UIMA
Issue Type: Bug
Components: addons, Sandbox-ConceptMapper
Affects Versions: 2.3.1Addons
Reporter: Jens Grivolla
Priority: Minor
Attachments: UIMA-2387.patch
Contrary to the documentation, the ResultingAnnotationName is not optional in
the ConceptMapper descriptor. In our use case we only want to write back
information to the original token, without creating a new annotation. Instead
of treating this as a documentation bug it is therefore better to fix the code.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
