the default handlers defined at lager.app overwrites handlers defined previously by application:set_env(lager, handlers, ...) if lager application is started application:start(lager)

Fixed typo in README.md

Fixed forgotten commas.

Added options parameter to lager:trace_file

Fix compile on Release 17 the right way.

Change a latin1 sequence so it is given as a list of integers. this avoids the problem entirely
since ASCII has the same representation in both latin1 and in utf-8

Use a binary rebar compiled with an older version of Erlang.

It has been compiled with R13B03 and resolves issue #183.

Make tests pass on buildbot more of the time

support disable pretty printing records encountered at compile time

Only discard gen_event notifications on high watermark

Previously all messages were being flushed, which meant that trapped exits
and internal gen_event messaging was also flushed, leading to undefined
behaviour.

closes #198

Fix: correct lager startup in crash_log test

Fixed empty tuple bug in lager:pr/2

Modified unit test to test 0 size tuple case.

Don't use the proplists module when decoding error_logger messages

Add newline to error_msg:error_report lines in crash.log, see #164

pretty printing of nested records

Fix lager_console_backend:is_new_style_console_available() function

Proplist module is a lot slower than lists:keyfind, which is a BIF,
because proplists has to work with 'bare' atoms as well as 2-tuples.

This should marginally improve the throughput when printing many
error_logger messages.

Add xref target, with exclusions

Remove the workaround for the bug when printing empty binaries in W mode

The fix for this was merged in R16 somewhere, so this workaround is no
longer needed, and fixes the EQC test from spotting the divergent
behaviour with io_lib.

See also: http://erlang.org/pipermail/erlang-patches/2012-September/003034.html

Fix dialyzer warnings and make all the records typed

Rework how dialyzer PLTs are built and used

This commit splits the PLTs into 2, one for all the required OTP
applications that are in the stdlib, and the other for the rebar
dependancies. Each one is created if it does not exist, then checked for
validity and then --add_to_plt is used to add any missing files (this is
very fast if nothing needs to be added). Then the application is
dialyzed using both PLTs.

The 'combo' PLT which resides in ~ is intended to be used by all of
Riak's deps, so it can grow to cover the set of OTP applications that
Riak depends on. Each project can only specify the ones it cares about.

Allow PLT destination to be specified

Fixed formatting.