The FreeMarkerAutoConfiguration logs a warning about missing templates even if the entire auto-configuration class is disabled via properties. I am using FreeMarker internally for non-Web reasons, but its presence triggers spurious warnings from the auto-configuration even after adding spring.freemarker.enabled: false.
Comment From: philwebb
The spring.freemarker.enabled property is somewhat poorly named. It's actually documented as "Whether to enable MVC view resolution for this technology".
I don't think we can apply the fix that you suggest because we have FreeMarkerNonWebConfiguration which will apply even if spring.freemarker.enabled is false and calls factory.setTemplateLoaderPaths(this.properties.getTemplateLoaderPath()); (via AbstractFreeMarkerConfiguration).
Setting spring.freemarker.check-template-location to false should stop the warning.
Comment From: chrylis
This behavior conflicts with general behavior of other enabled properties, which is to shut off the relevant auto-configuration bean registrations entirely. I'm aware that this is a backward-compatibility issue, but I suggest that for Boot 3 the property spring.freemarker.enabled should actually prevent Boot from registering any beans related to FreeMarker; as it is, I'd have to actively exclude the base auto-configuration class itself.