uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marshall Schor (JIRA)" <...@uima.apache.org>
Subject [jira] [Commented] (UIMA-346) Declaration of multiple externalResources with the same name is not reported as an error.
Date Wed, 12 Oct 2016 20:33:20 GMT

    [ https://issues.apache.org/jira/browse/UIMA-346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15569796#comment-15569796
] 

Marshall Schor commented on UIMA-346:
-------------------------------------

There is a use case where multiple definitions with the same name is used for overriding,
but it's not the recommended way (see the description).
Given this, I'm +0 for increasing the level of the message from warning to severe.
I'm -0 for adding a (by default, off) mode (via another -D parameter or via "additional parameters"
mechanism, or both) for "strict descriptor checking"; I think the complexity it adds is not
worth the benefit, since it will usually be off (because people won't set it).

Other opinions?

> Declaration of multiple externalResources with the same name is not reported as an error.
> -----------------------------------------------------------------------------------------
>
>                 Key: UIMA-346
>                 URL: https://issues.apache.org/jira/browse/UIMA-346
>             Project: UIMA
>          Issue Type: Bug
>          Components: Core Java Framework
>    Affects Versions: 2.3
>            Reporter: Adam Lally
>            Priority: Minor
>              Labels: Resources
>
> A user reports that it is difficult to debug a situation where developers have accidentally
declared two resources with the same name.  UIMA currently logs a WARNING message in this
case.
> The severity could be increased to SEVERE.  Also we could add a "strict descriptor checking"
mode (off by default) that throws an Exception in this case, and possibly other cases.  We
probably shouldn't have this on by default since it could break existing applications that
currently work.
> Also our documentation should say that qualified names should be used for resources,
e.g. org.myorg.myproj.myresource, to minimize the chance of accidental name clashes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message