I was supposing that the utility configuration was a 1.7 hack, not 1.6.The adaptation is, of course, backwards compatible, and very convenient for organizations that are using MMBase 1.6 in a production environment.
I don't really mind (as long as config files are not required to be present, so the system is backwards compatible), but I suggest that, unless specified explicitly in a call, hacks are intended for the CVS Head version (1.7), and not for the patch. If people agree, this would make voting for hacks a bit more transparent.
But has it been documented in the releasenotes a new configuration file is needed? We must try and keep the upgrade process between minor releases as simple as possible, only replacing the jar would be the best solution. Sometimes a configuration of html change is needed, but it has to be documented, so people will know what to do.
Gerard
