incubator-ctakes-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Finan (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CTAKES-164) UMLS password could not be set in shell as ctakes.umlspw
Date Wed, 20 Feb 2013 17:25:13 GMT

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

Sean Finan resolved CTAKES-164.
-------------------------------

    Resolution: Fixed

User can use underscore character in place of dot character in environment variable names.
 Lookup will proceed with dot first and only lookup via underscore when dot equivalent does
not exist.  For instance, if the variable ctakes.umlspw exists then it is used.  If it does
not exist but ctakes_umlspw exists then ctakes_umlspw is used.
                
> UMLS password could not be set in shell as ctakes.umlspw
> --------------------------------------------------------
>
>                 Key: CTAKES-164
>                 URL: https://issues.apache.org/jira/browse/CTAKES-164
>             Project: cTAKES
>          Issue Type: Improvement
>          Components: ctakes-dictionary-lookup, ctakes-utils
>    Affects Versions: 3.1-incubating
>         Environment: bash
>            Reporter: Sean Finan
>            Priority: Minor
>              Labels: features
>             Fix For: 3.1-incubating
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> The setting of passwords etc. is allowable outside .xml descriptor files by setting an
environment variable with the name of the value required in the xml file.  For instance, umls
dictionary lookup required a password to be set in the .xml as ctakes.umlspw OR in the environment
as ctakes.umlspw
> Unfortunately, setting a variable with a dot in the name is difficult in some shell environments.
> Allow the user to set variables in their environment with an underscore in place of the
dot, such as ctakes_umlspw

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message