You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Richard Eckart de Castilho (JIRA)" <de...@uima.apache.org> on 2016/09/02 17:45:20 UTC

[jira] [Updated] (UIMA-346) Declaration of multiple externalResources with the same name is not reported as an error.

     [ https://issues.apache.org/jira/browse/UIMA-346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Richard Eckart de Castilho updated UIMA-346:
--------------------------------------------
    Labels: Resources  (was: )

> 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)