[jira] Commented: (UIMA-999) Should have a way to ignore or omit the imports in an aggregate that will be overridden by the deployment descriptor

["Marshall Schor (JIRA)" <ui...@incubator.apache.org>]

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

Marshall Schor commented on UIMA-999:
-------------------------------------

Even if the imports are overridden when deploying as an async delegate, these imports still would be used if the descriptor was run using the DocumentAnalyzer or CVD, or run using uima-as with the aggregate in the "async=false" mode.  

It is true that if you have a descriptor which you know will *never* be run in these modes,then, specifying the imports is redundant.  

Is the intent of this to somehow document that in the descriptor (other than as a comment - which could be done, especially if Jira issue http://issues.apache.org/jira/browse/UIMA-239 was done)?

> Should have a way to ignore or omit the imports in an aggregate that will be overridden by the deployment descriptor
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: UIMA-999
>                 URL: https://issues.apache.org/jira/browse/UIMA-999
>             Project: UIMA
>          Issue Type: Bug
>          Components: Async Scaleout
>            Reporter: Burn Lewis
>            Priority: Minor
>
> Entries in the deployment descriptor for a delegate override the import specified in the aggregate descriptor for that delegate ... but the import must still be present and valid.  It would be nice to have a way to indicate that such imports will be overriden and should be ignored.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.