You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Burn Lewis (JIRA)" <de...@uima.apache.org> on 2013/02/22 14:08:13 UTC
[jira] [Commented] (UIMA-2686) Derive DUCC_HOME from the location
of executable jars in CLI.
[ https://issues.apache.org/jira/browse/UIMA-2686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13584241#comment-13584241 ]
Burn Lewis commented on UIMA-2686:
----------------------------------
I suggest exchanging 1 & 2 so the search is from the inside out ... first Java's properties, then the environment, then the filesystem. Also callers can set system properties but can't change the environment.
> Derive DUCC_HOME from the location of executable jars in CLI.
> --------------------------------------------------------------
>
> Key: UIMA-2686
> URL: https://issues.apache.org/jira/browse/UIMA-2686
> Project: UIMA
> Issue Type: Task
> Components: DUCC
> Reporter: Jim Challenger
> Assignee: Jim Challenger
>
> The scripting currently derives the location of DUCC_HOME based on where it is invoked from. When using the API the invoked code should do the same thing, based on where it is invoked from.
> A search-order is established:
> 1) search environment for DUCC_HOME
> 2) look in system properties (-DDUCC_HOME)
> 3) infer DUCC_HOME from the location of the jar file the API is invoked from
> If DUCC_HOME is not found in any of these places, throw and fail.
--
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