config standards

Fine, there are dozens of settings files, among them are application components settings

• crowd.properties for crowd service
• crowd.properties for crowd client
• build.properties for application itself
• server.xml - for Tomcat
• ... and so on

Can all this be concentrated just in one file having self-explanatory sections?

Or, at least, at one folder, having files with self-explanatory names?

What about config includes support?

Wouldn't it be better if all configs retain one format (fine then, let it be XML, not JSON or INI)?

Why should I store domain and port settings for service at crowd.properties instead of Tomcat server.xml (what seems to me slightly more convenient)?

I think, configuration process will be much more easier after these optimizations, however, maybe, I'm wrong, and there is reason to have several configs with same logics and same names in several dirs

Maybe, the best way to implement is to concentrate as much configuration as possible at web-interface?