Ferdinand Soethe wrote: > > In fact having re-read all of this I'd go another step and suggest > something like this (* = my reasons for this). > > my-project/ > forrest.properties to become forrest-properties.xml > *you know what is is right away > > all other config files > *why not keep them in the root > much easier to find. no clutter to be expected > because there are not so many > > CatalogManager.properties > *why have a subdir just for one file?
See the comment earlier in the thread, copied here: >The CatalogManager.properties file needs to be >available on the classpath when Cocoon starts. >Can we move it to the new conf directory and >have the classpath point to that location? So if someone can change the build system so that this file gets picked up by Java from a different location, then fine. --David