river-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peter Firmstone (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (RIVER-193) support declaring entries in a "common" configuration source for use in other configuration sources
Date Sat, 05 Dec 2015 11:01:10 GMT

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

Peter Firmstone resolved RIVER-193.
-----------------------------------
       Resolution: Won't Fix
    Fix Version/s: River_3.0.0

Use Groovy configuration instead.

> support declaring entries in a "common" configuration source for use in other configuration
sources
> ---------------------------------------------------------------------------------------------------
>
>                 Key: RIVER-193
>                 URL: https://issues.apache.org/jira/browse/RIVER-193
>             Project: River
>          Issue Type: Improvement
>          Components: net_jini_config
>            Reporter: Brian Murphy
>             Fix For: River_3.0.0
>
>
> Bugtraq ID [6230095|http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6230095]
> Related Bugs	
> Submit Date	16-FEB-2005
> Description	
> There seems to be some demand for declaring entries in a common configuration 
> file for use in other configuration files.  This feature would minimize the number of

> files that need to be changed when going from one deployment to the next.
> Work Around	
> N/A



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

Mime
View raw message