Attach shaded jar.
Create a shaded version with relocated dependencies. logback and slf4j-api not included, as these
are often part of the container.
adding support for Markers as @tags.
adding support for Markers as @tags.
Merge pull request #6 from mfriedenhagen/shaded

Create a shaded jar as drop-in for e.g. artifactory
Updating CONTRIBUTORS
Merge pull request #8 from schup/master

Added includeCallerInfo flag to disable expensive calculation of caller information.
Updating CONTRIBUTORS
Merge pull request #10 from phasebash/markers-as-tags

Create LogStash tags from SLF4J Markers
Merge branch 'master' of github.com:logstash/logstash-logback-encoder
Updating CONTRIBUTORS
Little tidy up
[maven-release-plugin] prepare release logstash-logback-encoder-1.3
[maven-release-plugin] prepare for next development iteration
Move logstash formatting logic out of logstash encoder

This allows it to be reused in other components.
Obvious layout implementation using logstash formatter
Implement socket appender on top of the syslog implementation

It turns out that the syslog base is not syslog-specific, but just ships
the data in any given layout over UDP. (The facilty / severity are not
used in the default implementation.)

If you configure logstash like so:

    input {
      udp {
        port => 5515
        format => json_event
        tag => my_tag_for_logback_events
      }
    }

and logback like so:

    <appender name="LOGSTASH" class="net.logstash.logback.appender.LogstashSocketAppender">
      <host>my.logstash.server.local</host>
      <port>5515</port>
    </appender>

log messages will be sent directly to the server, with no need for a
logstash daemon running locally.
Merge pull request #11 from bkirwi/push-logs

Push logs
Update contributors
I hate Maven sometimes