search

jbake-org / jbake

Java based open source static site/blog generator for developers & designers.
http://jbake.org
MIT License
1.12k stars 326 forks source link

Include stack trace in log file when template engine can't be found #634

Open jonbullock opened 4 years ago

jonbullock commented 4 years ago

Relates to #602

Stack trace should be output in a log file somewhere even if it's not logged to the console.

pzygielo commented 3 years ago

Please, consider changing level used in l.82 (to info or perhaps better - to debug) in https://github.com/jbake-org/jbake/blob/4007fd2296ac03181fcf0fe32dd026d5c941bb0b/jbake-core/src/main/java/org/jbake/template/TemplateEngines.java#L74-L85

As current issue is continuation of #602, I'm not sure if this deserves separate one or could be covered here.

In my maven project following is reported

[INFO] --- jbake-maven-plugin:0.3.4:generate (build-site) @ xxx ---
[WARNING] Template engine not available: org.jbake.template.GroovyMarkupTemplateEngine
[WARNING] Template engine not available: org.jbake.template.PebbleTemplateEngine
[WARNING] Template engine not available: org.jbake.template.GroovyTemplateEngine
[WARNING] Template engine not available: org.jbake.template.ThymeleafTemplateEngine
[WARNING] Template engine not available: org.jbake.template.JadeTemplateEngine
[INFO] Baking has started...

as I have only freemarker added as dependency. (No other engines are needed.) Thus above warnings.

To get rid of them I could add the remaining engines, but I don't want to have unused dependencies to maintain. If I have no required engine - I expect the error, and that's the case once I remove freemarker.

That's why I think it shall be either info, if it is so important, or rather debug only - to be used in investigation when actually needed engine can't be found. Not always.