[ http://issues.apache.org/jira/browse/CONFIGURATION-216?page=comments#action_12417354 ]
Oliver Heger commented on CONFIGURATION-216: -------------------------------------------- You are right! The problem did not occur to me because I use the maven build. And after a maven build ran successfully the ant build is successful, too, because maven copies the files to the right location. Well, I changed the copying stuff in build.xml, and now both builds should work. Sorry! > Inconsistent way to locate filename when creating configuration > --------------------------------------------------------------- > > Key: CONFIGURATION-216 > URL: http://issues.apache.org/jira/browse/CONFIGURATION-216 > Project: Commons Configuration > Type: Bug > Environment: commons-configuration-1.3-dev > Reporter: Gabriele Garuglieri > Assignee: Oliver Heger > Priority: Minor > > 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/conf1.properties" exists in classpath: > PropertiesConfiguration pc = new > PropertiesConfiguration("conf/conf1.properties"); > gives org.apache.commons.configuration.ConfigurationException: Cannot locate > configuration source conf1.properties > while > PropertiesConfiguration pc = new PropertiesConfiguration(); > pc.setFileName("conf/conf1.properties"); > 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: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
