commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oliver Heger (JIRA)" <>
Subject [jira] Commented: (CONFIGURATION-216) Inconsistent way to locate filename when creating configuration
Date Thu, 24 Aug 2006 06:48:37 GMT
Oliver Heger commented on CONFIGURATION-216:

Patch applied. Many thanks!

I made the following minor changes:
- Changed the visibility of ConfigurationUtils.locateFromClasspath() to package scope; there
is no need to make this method part of the public API.
- Excluded the tests that try to access the jar file. We had some trouble with this jar (see
ticket CONFIGURATION-71), which I don't want to have again.

Regarding JMXConfiguration: That would be really cool. JMX is on our roadmap for future releases.

> Inconsistent way to locate filename when creating configuration
> ---------------------------------------------------------------
>                 Key: CONFIGURATION-216
>                 URL:
>             Project: Commons Configuration
>          Issue Type: Bug
>         Environment: commons-configuration-1.3-dev
>            Reporter: Gabriele Garuglieri
>         Assigned To: Oliver Heger
>            Priority: Minor
>         Attachments: 216-1.patch, resources.jar
> There is a different behaviour locating the configuration file in classpath depending
on the way it is set in the configuration class.
> For example assuming "conf/" exists in classpath:
> PropertiesConfiguration pc = new PropertiesConfiguration("conf/");
> gives org.apache.commons.configuration.ConfigurationException: Cannot locate configuration
> while
> PropertiesConfiguration pc = new PropertiesConfiguration();
> pc.setFileName("conf/");
> pc.load();
> properly locate file in classpath and loads it.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message