A better logging approach about gizmo

[ifesdjeen]

I would say that testing logging is not really necessary.
It's enough to just make it work fine.

Seems that for gizmo-web-template we only need to provide a new release. I'll do that as soon as we have a stable working version.

[ujh]

I finally had some time to look at this again. Changing the code in loggin.clj to use timbre was no problem. Unfortunately just adding the dependency to project.clj in gizmo didn't work (leiningen couldn't find timbre). So I had to add it to gizmo-cloc and gizmo-web-template, too.

gizmo commits: https://github.com/ujh/gizmo/commits/feature/logging
gizmo-cloc commit: ujh/gizmo-cloc@dc1f9955e9591223d9a7596c2f01a0540692648f
gizmo-web-template commit: ujh/gizmo-web-template@6e88c818e74460a61faf23b7a96c597df4dc441e

This of course is only the minimal solution. Should I have a look at the timbre configuration options and if it's possible to configure the logging in the environment? Just like jetty is configured in development.clj? The fact that timbre is essentially configured through a global system (@timbre/config, timbre/set-level!, ...) isn't very encouraging though.

[ifesdjeen]

Oh my, somehow I completely missed your commits :/

[ujh]

Not to worry Alex, I've been swamped with work right after finishing this anyway.

[ifesdjeen]

Merged!