diff --git a/logback-site/src/site/pages/manual/appenders.html b/logback-site/src/site/pages/manual/appenders.html index 2dfd52b29a..bfa6a87b49 100755 --- a/logback-site/src/site/pages/manual/appenders.html +++ b/logback-site/src/site/pages/manual/appenders.html @@ -42,8 +42,7 @@

Chapter 4: Appenders

-

What is an Appender?

+

What is an Appender?

Logback delegates the task of writing a logging event to components called appenders. Appenders must implement the Marker-based

- -

Authentication/STARTTLS/SSL

+

Authentication/STARTTLS/SSL

SMTPAppender supports authentication via plain user passwords as well as both the STARTTLS and SSL diff --git a/logback-site/src/site/pages/manual/architecture.html b/logback-site/src/site/pages/manual/architecture.html old mode 100644 new mode 100755 index 242fc2a53f..141aa909da --- a/logback-site/src/site/pages/manual/architecture.html +++ b/logback-site/src/site/pages/manual/architecture.html @@ -82,8 +82,7 @@

Logger, Appenders and Layouts

loggers.

-

Logger context

+

Logger context

The first and foremost advantage of any logging API over plain System.out.println resides in its ability to disable @@ -149,9 +148,8 @@

Effective Level aka Level Inheritance -

+

Effective Level aka + Level Inheritance

Loggers may be assigned levels. The set of possible levels (TRACE, DEBUG, INFO, WARN and ERROR) are defined in the @@ -330,9 +328,8 @@

X, which has an assigned level.

-

Printing methods and the basic selection - rule

+

Printing methods and + the basic selection rule

By definition, the printing method determines the level of a logging request. For example, if L is a logger @@ -662,8 +659,8 @@

-

Parameterized logging

+

Parameterized + logging

Given that loggers in logback-classic implement the SLF4J's @@ -841,8 +838,7 @@

6. Sending out the LoggingEvent

-

Performance

+

Performance

One of the often-cited arguments against logging is its computational cost. This is a legitimate concern as even diff --git a/logback-site/src/site/pages/manual/configuration.html b/logback-site/src/site/pages/manual/configuration.html index c2908696ce..ddbb9a47c9 100755 --- a/logback-site/src/site/pages/manual/configuration.html +++ b/logback-site/src/site/pages/manual/configuration.html @@ -49,8 +49,8 @@

Chapter 3: Logback configuration

-

Configuration in logback

+

Configuration in + logback

Inserting log requests into the application code requires a fair amount of planning and effort. Observation shows that @@ -120,8 +120,8 @@

-

Automatically configuring logback

+

Automatically + configuring logback

The simplest way to configure logback is by letting logback fall back to its default configuration. Let us give a taste of how @@ -255,8 +255,7 @@

Automatic configuration with logback-test.xml or directory accessible from the class path. Running the MyApp1 application should give identical results to its previous run.

-

Automatic +

Automatic printing of status messages in case of warning or errors

If warning or errors occur during the parsing @@ -381,9 +380,9 @@

-

Specifying the location of the default - configuration file as a system property

+

Specifying the + location of the default configuration file as a system + property

You may specify the location of the default configuration file with a system property named @@ -400,9 +399,8 @@

-

Automatically reloading configuration file upon - modification

+

Automatically reloading + configuration file upon modification

Logback-classic can scan for changes in its configuration file and automatically reconfigure itself when the @@ -489,9 +487,8 @@

Invoking JoranConfigurator - directly

+

Invoking + JoranConfigurator directly

Logback relies on a configuration library called Joran, part of logback-core. Logback's default configuration mechanism invokes @@ -552,12 +549,8 @@

context.reset() invocation should be omitted.

-

Viewing - status messages -

- - +

Viewing status + messages

Logback collects its internal status data in a StatusManager @@ -600,9 +593,8 @@

http://host/yourWebapp/lbClassicStatus

-

Listening to status messages -

+

Listening to status + messages

You may also attach a StatusListener to a StatusManager so that you can take immediate action in @@ -649,9 +641,9 @@

-

"logback.statusListenerClass" system property -

+

"logback.statusListenerClass" system + property

One may also register a status listener by setting the "logback.statusListenerClass" Java system property to the name of @@ -679,9 +671,11 @@

java -Dlogback.statusListenerClass=ch.qos.logback.core.status.NopStatusListener ...

-

Configuration file syntax -

+ +

Stopping + logback-classic

+ +

Configuration file syntax

As you have seen thus far in the manual with plenty of examples still to follow, logback allows you to redefine logging behavior @@ -720,10 +714,9 @@

camelCase convention which is almost always the correct convention.

-

Case sensitivity of tag names

+

Case sensitivity of + tag names

-

Since logback version 0.9.17, tag names pertaining to explicit rules are case insensitive. For example, <logger>, <Logger> and <LOGGER> are valid configuration elements and will @@ -744,9 +737,8 @@

-

Configuring loggers, or the - <logger> element

+

Configuring loggers, or + the <logger> element

At this point you should have at least some understanding of level inheritance and @@ -785,9 +777,8 @@

Configuring the root logger, or the - <root> element

+

Configuring the root + logger, or the <root> element

The <root> element configures the root logger. It supports a single attribute, namely the Example - even if the Java source code does not directly refer to it.

-

Configuring +

Configuring Appenders

An appender is configured with the <appender> @@ -1115,8 +1105,7 @@

-

Appenders accumulate +

Appenders accumulate

By default, appenders are cumulative: a logger will log to @@ -1209,9 +1198,8 @@

myApp.log file.

-

Overriding - the default cumulative behaviour

+

Overriding the + default cumulative behaviour

In case the default cumulative behavior turns out to be unsuitable for your needs, you can override it by setting the @@ -1261,9 +1249,8 @@

foo.log file and only in that file.

- -

Setting the context name

+

Setting the context + name

As mentioned in an earlier chapter, every logger is attached to a logger @@ -1301,9 +1288,7 @@

- -

Variable +

Variable substitution

Note Earlier versions of this document @@ -1336,9 +1321,7 @@

As they often come in handy, the HOSTNAME and CONTEXT_NAME variables are automatically defined and have context scope.

- -

Defining variables

+

Defining variables

Variables can be defined one at a time in the configuration file itself or loaded wholesale from an external properties file or an @@ -1457,8 +1440,7 @@

-

Scopes

+

Scopes

A property can be defined for insertion in local scope, in context scope, or in system scope. Local scope @@ -1534,9 +1516,8 @@

-

Default - values for variables

+

Default values + for variables

Under certain circumstances, it may be desirable for a variable to have a default value if it is not declared or its value is @@ -1547,8 +1528,7 @@

"${aName:-golden}" will be interpreted as "golden".

-

Nested variables

+

Nested variables

Variable nesting is fully supported. Both the name, default-value and value definition of a variable can reference @@ -1615,23 +1595,20 @@

default value nesting

-

HOSTNAME property

+

HOSTNAME property

As it often comes in handy, the HOSTNAME property is defined automatically during configuration with context scope.

-

CONTEXT_NAME property

+

CONTEXT_NAME property

As its name indicates, the CONTEXT_NAME property corresponds to the name of the current logging context.

-

Setting a timestamp

+

Setting a timestamp

The timestamp element can define a property according to current date and time. The timestamp element is .

-

Defining +

Defining properties on the fly

You may define properties dynamically using the @@ -1711,9 +1687,8 @@

-

Conditional processing of configuration - files

+

Conditional processing of + configuration files

Developers often need to juggle between several logback configuration files targeting different environments such as @@ -1804,8 +1779,8 @@

-

Obtaining variables from JNDI

+

Obtaining variables from + JNDI

Under certain circumstances, you may want to make use of env-entries stored in JNDI. The <insertFromJNDI> @@ -1843,8 +1818,7 @@

-

File inclusion

+

File inclusion

Joran supports including parts of a configuration file from another file. This is done by declaring a <include> @@ -1920,8 +1894,8 @@

<include optional="true" ..../> -

Adding a context listener

+

Adding a context + listener

Instances of the LoggerContextListener @@ -1935,9 +1909,8 @@

subsequent chapter.

-

LevelChangePropagator

+

LevelChangePropagator

As of version 0.9.25, logback-classic ships with LevelChangePropagator, diff --git a/logback-site/src/site/pages/manual/introduction.html b/logback-site/src/site/pages/manual/introduction.html old mode 100644 new mode 100755 index 0eb94f552e..e5fd643ef7 --- a/logback-site/src/site/pages/manual/introduction.html +++ b/logback-site/src/site/pages/manual/introduction.html @@ -220,20 +220,7 @@

Requirements

-

Building logback

- - - +

Building logback

As its build tool, logback relies on Maven, a widely-used open-source diff --git a/logback-site/src/site/pages/reasonsToSwitch.html b/logback-site/src/site/pages/reasonsToSwitch.html old mode 100644 new mode 100755 index 79506a2d0d..fc9570b6d3 --- a/logback-site/src/site/pages/reasonsToSwitch.html +++ b/logback-site/src/site/pages/reasonsToSwitch.html @@ -31,16 +31,14 @@

Reasons to prefer logback over log4j

will probably love logback.

-

Faster implementation

+

Faster implementation

Based on our previous work on log4j, logback internals have been re-written to perform about ten times faster on certain critical execution paths. Not only are logback components faster, they have a smaller memory footprint as well.

-

Extensive - battery of tests

+

Extensive battery of tests

Logback comes with a very extensive battery of tests developed over the course of several years and untold hours of work. While @@ -51,8 +49,8 @@

Extensive conditions.

-

logback-classic speaks SLF4J natively

+

logback-classic speaks SLF4J + natively

Since the Logger class in logback-classic implements the SLF4J API natively, you incur zero overhead when @@ -65,14 +63,13 @@

-

Extensive documentation

+

Extensive documentation

Logback ships with detailed and constantly updated documentation.

-

Configuration files in XML or Groovy

+

Configuration files in XML or + Groovy

The traditional way of configuring logback is via an XML file. Most of the examples in the documentation use this XML @@ -90,9 +87,8 @@

.

-

Automatic reloading of configuration - files

+

Automatic reloading of + configuration files

Logback-classic can automatically reload its @@ -104,8 +100,8 @@

-

Graceful recovery from I/O failures

+

Graceful recovery from I/O + failures

Logback's FileAppender and all its sub-classes, including RollingFileAppender, can gracefully recover @@ -116,8 +112,8 @@

-

Automatic removal of old log archives

+

Automatic removal of old + log archives

By setting the maxHistory property of -

Automatic compression of archived log - files

+

Automatic compression of + archived log files

RollingFileAppender @@ -143,8 +138,7 @@

-

Prudent mode

+

Prudent mode

In prudent mode, multiple FileAppender instances running on multiple @@ -153,17 +147,15 @@

RollingFileAppender.

-

Lilith

+

Lilith

Lilith is a logging and access event viewer for logback. It is comparable to log4j's chainsaw, except that Lilith is designed to handle large amounts of logging data without flinching.

-

Conditional processing of configuration - files

+

Conditional processing of + configuration files

Developers often need to juggle between several logback configuration files targeting different environments such as @@ -178,8 +170,7 @@

-

Filters

+

Filters

Logback comes with a wide array of filtering capabilities going much @@ -212,8 +203,7 @@

-

SiftingAppender

+

SiftingAppender

SiftingAppender @@ -224,9 +214,8 @@

-

Stack traces with packaging data -

+

Stack traces with + packaging data

When logback prints an exception, the stack trace will include packaging data. Here is a sample stack trace generated by the .

-

Logback-access, i.e. HTTP-access logging with - brains, is an integral part of logback

+

Logback-access, + i.e. HTTP-access logging with brains, is an integral part of + logback

Last but not least, the logback-access module, part of the logback distribution, integrates with Servlet containers such as @@ -275,8 +264,7 @@

-

In summary

+

In summary

We have listed a number of reasons for preferring logback over log4j. Given that logback builds upon on our previous work on