You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@oodt.apache.org by "Andrew Hart (Resolved) (JIRA)" <ji...@apache.org> on 2011/11/24 00:00:45 UTC
[jira] [Resolved] (OODT-343) Add support for basic 'environment
replacement' in module config.ini files
[ https://issues.apache.org/jira/browse/OODT-343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Hart resolved OODT-343.
------------------------------
Resolution: Fixed
patch applied in r1205647
> Add support for basic 'environment replacement' in module config.ini files
> --------------------------------------------------------------------------
>
> Key: OODT-343
> URL: https://issues.apache.org/jira/browse/OODT-343
> Project: OODT
> Issue Type: Improvement
> Components: balance
> Affects Versions: 0.3
> Environment: n/a
> Reporter: Andrew Hart
> Assignee: Andrew Hart
> Fix For: 0.4
>
> Attachments: OODT-343.Hart.110311.patch.txt
>
>
> One of the principles of OODT Balance is that it should be possible to drop in modules with minimal configuration. One thing that currently frustrates this is occasional the need, in a module's configuration file, to know the actual install path or url of the module. Introducing a limited set of basic "environment variables," which would be evaluated just prior to parsing the module config file, would remove the need to know, a-priori, where the module has been installed.
> For starters, the following "environment variables" should be available:
>
> [MODULE_PATH] should expand/evaluate to the file system path of the module
> [MODULE_ROOT] should expand/evaluate to the url base of the module
> [MODULE_STATIC] should expand/evaluate to the url base of the module's static assets directory (css, js, img, etc)
> These "environment variables" can then be used in module configuration files wherever absolute paths/urls would otherwise have been needed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira