Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Message-ID: <34227009.1238186750926.JavaMail.jira@brutus>
Date: Fri, 27 Mar 2009 13:45:50 -0700 (PDT)
From: "Ralph Goers (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Subject: [jira] Resolved: (CONFIGURATION-340) Allow configuration files to
 be stored in many locations
In-Reply-To: <1758616380.1223968184397.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Ralph Goers resolved CONFIGURATION-340.
---------------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 2.0)
                   1.7

This has been committed to both trunk and the experimental branch.

> Allow configuration files to be stored in many locations
> --------------------------------------------------------
>
>                 Key: CONFIGURATION-340
>                 URL: https://issues.apache.org/jira/browse/CONFIGURATION-340
>             Project: Commons Configuration
>          Issue Type: Improvement
>    Affects Versions: 1.5
>         Environment: All
>            Reporter: Ralph Goers
>             Fix For: 1.7
>
>
> AbstractFileConfiguration currently gets or stores files on the local file system or via http. Commons Configuration should be enhanced so that files can be stored or retrieved using almost any mechanism. For example, using Commons VFS or constructs like Maven's Wagon would allow files to be housed in a source control system, a CMS, a database or anything else one could dream up. This is important to me as I need to be able to store and retrieve my configuration files using WebDav (with CHECKIN and CHECKOUT). 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.