logback  1.2.3
About: Logback is a generic Logging Framework (intended as a log4j successor).
  Fossies Dox: logback-1.2.3.tar.gz  ("inofficial" and yet experimental doxygen-generated source code documentation)  

logback Documentation

Some Fossies usage hints in advance:

  1. To see the Doxygen generated documentation please click on one of the items in the steelblue colored "quick index" bar above or use the side panel at the left which displays a hierarchical tree-like index structure and is adjustable in width.
  2. If you want to search for something by keyword rather than browse for it you can use the client side search facility (using Javascript and DHTML) that provides live searching, i.e. the search results are presented and adapted as you type in the Search input field at the top right.
  3. Doxygen doesn't incorporate all member files but just a definable subset (basically the main project source code files that are written in a supported language). So to search and browse all member files you may visit the Fossies
  4. logback-1.2.3.tar.gz contents page and use the Fossies standard member browsing features (also with source code highlighting and additionally with optional code folding).
README.md

#About logback

Thank you for your interest in logback, the reliable, generic, fast and flexible logging library for Java.

The Logback documentation can be found on the project web-site as well as under the docs/ folder of the logback distribution.

#Building logback

Building logback is documented at:

https://logback.qos.ch/setup.html#ide

#In case of problems

In case of problems please do not hesitate to post an e-mail message on the logback-user@qos.ch mailing list. However, please do not directly e-mail logback developers. The answer to your question might be useful to other users. Moreover, there are many knowledgeable users on the logback-user mailing lists who can quickly answer your questions.

#Pull requests

If you are interested in improving logback, great! The logback community looks forward to your contribution. Please follow this process:

  1. Please file a bug report. Pull requests with an associated JIRA issue will get more attention.

    Optional: Start a discussion on the logback-dev mailing list about your proposed change.

  2. Fork qos-ch/logback. Ideally, create a new branch from your fork for your contribution to make it easier to merge your changes back.

  3. Make your changes on the branch you hopefuly created in Step 2. Be sure that your code passes existing unit tests.

  4. Please add unit tests for your work if appropriate. It usually is.

  5. Push your changes to your fork/branch in github. Don't push it to your master! If you do it will make it harder to submit new changes later.

  6. Submit a pull request to logback from from your commit page on github.

Build Status

Build Status