Just released ring-logger 0.6.2 with a bugfix for the OneLog
implementation. Use this release if you are going to use it with
OneLog, or wait until the 0.7.0 release which should happen soon.

# Changelog

## 0.6.2

* Fix OneLog implementation: error -> error-with-ex

## 0.6.1

* Add ability to customize messages & to disable coloring


On Mon, Aug 31, 2015 at 3:31 PM, Nicolás Berger <nicober...@gmail.com> wrote:
> I'm glad to announce the release of ring-logger 0.6.1
>
> Ring-logger is a fork of pjlegato's ring.middleware.logger that aims
> to make it easier to switch the logging infrastructure (from onelog to
> taoensso/timbre, the now default tools.logging or any other),
> customize the logging output (coloring/no-coloring, turn off or
> customize specific messages) and much more!
>
> clojars coordinates: [ring-logger "0.6.1"]
> github: https://github.com/nberger/ring-logger/releases/tag/0.6.1
>
> Usage & migration from r.m.logger instructions, customization
> examples, roadmap and much more can be found in
> https://github.com/nberger/ring-logger
>
> I'd like to thank Paul Legato for building ring.middleware.logger
> without which ring-logger would not exist. I think r.m.logger is a
> perfectly valid option if you don't mind pulling dependencies from
> OneLog.
>
> Feedback and contributions are more than welcome!
>
> -
> Nicolás

-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to