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/09 17:47:22 UTC

[jira] [Updated] (UIMA-1035) CDE support for envVarRef

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

Richard Eckart de Castilho updated UIMA-1035:
---------------------------------------------
    Labels: Stale  (was: )

This issue is marked as "stale" due to inactivity for 5 years or longer. If no further activity is detected on this issue, it is scheduled be closed as 'unresolved' in 3 months time from now (Dec 2016).

> CDE support for envVarRef
> -------------------------
>
>                 Key: UIMA-1035
>                 URL: https://issues.apache.org/jira/browse/UIMA-1035
>             Project: UIMA
>          Issue Type: Improvement
>          Components: Eclipse plugins
>    Affects Versions: 2.2.2, 2.3
>            Reporter: Marshall Schor
>            Priority: Minor
>              Labels: Stale
>
> The Component Descriptor Editor (CDE) has never supported envVarRef - this is the capability to have environmental variables substituted at read-time for certain parts of the descriptor.  The CDE design philosophy is such that it attempts to validate Component Descriptors at edit time.  Some compromise should be figured out so that users who are using envVarRef can get some value from the CDE, and furthermore, the CDE should not remove <envVarRef> elements from the descriptor.



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