This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Logback: the generic, reliable, fast and flexible logging framework.". The branch, master has been updated via 218b66b5c0c7826c39abbc02e3728ad171bba8f8 (commit) via b05d1c484c617f22522dd2094a04f87a78447afe (commit) from 02da05ef77822b6b78669c65ab463f8f3f2240ba (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- http://git.qos.ch/gitweb/?p=logback.git;a=commit;h=218b66b5c0c7826c39abbc02e... http://github.com/ceki/logback/commit/218b66b5c0c7826c39abbc02e3728ad171bba8... commit 218b66b5c0c7826c39abbc02e3728ad171bba8f8 Merge: 02da05e b05d1c4 Author: Ceki Gulcu <ceki@qos.ch> Date: Thu Jun 16 11:35:39 2011 +0200 Merge branch 'typo_fixes' of git://github.com/datafueled/logback diff --cc logback-site/src/site/pages/news.html index 58e1821,a4f41e6..fb530d1 --- a/logback-site/src/site/pages/news.html +++ b/logback-site/src/site/pages/news.html @@@ -40,27 -40,17 +40,27 @@@ MDC.clear operation. This issue was reported in <a href="http://jira.qos.ch/browse/LBCLASSIC-253">LBCLASSIC-253</a> by Tommy Becker and independently fixed by the changes designated - to fix LBCLASSIC-254</p>. + to fix LBCLASSIC-254.</p> + + <p>As reported by Deepak Vadgama in <a + href="http://jira.qos.ch/browse/LBCORE-199">LBCORE-199</a>, the + entry in every zip file created by + <code>FixedWindowRollingPolicy</code> had the same name. The issue + was solved by adding a timestamp to the name of the entry in the + zip files as suggested by a Benoit Xhenseval.</p> <p><code>ConfigurationWatchList</code> no longer emits an error - message when it encouters a configuraton file placed in a jar + message when it encounters a configuration file placed in a jar file, fixing <a href="http://jira.qos.ch/browse/LBCLASSIC-246">LBCLASSIC-246</a> - as reported by Joern Huxhorn. + as reported by Joern Huxhorn. This release also fixes <a + href="http://jira.qos.ch/browse/LBCLASSIC-247">LBCLASSIC-247</a> + reported by Michael Franz. </p> + <p>Logback now emits a clearer error message in case a conversion - pattern misses a closing parenthesis or if an openening + pattern misses a closing parenthesis or if an opening parenthesis is misplaced. This fixes <a href="http://jira.qos.ch/browse/LBCORE-193">LBCORE-193</a> reported by B. K. Oxley.</p> http://git.qos.ch/gitweb/?p=logback.git;a=commit;h=b05d1c484c617f22522dd2094... http://github.com/ceki/logback/commit/b05d1c484c617f22522dd2094a04f87a78447a... commit b05d1c484c617f22522dd2094a04f87a78447afe Author: Bruce Mitchener <bruce.mitchener@gmail.com> Date: Mon May 2 13:49:27 2011 +0700 Fix typos. diff --git a/logback-access/src/main/java/ch/qos/logback/access/pattern/NAConverter.java b/logback-access/src/main/java/ch/qos/logback/access/pattern/NAConverter.java index e234c90..ed1f7a5 100644 --- a/logback-access/src/main/java/ch/qos/logback/access/pattern/NAConverter.java +++ b/logback-access/src/main/java/ch/qos/logback/access/pattern/NAConverter.java @@ -19,7 +19,7 @@ import ch.qos.logback.access.spi.IAccessEvent; * Always returns the NA (not available) string which is "-" in the case * of access conversions. * - * @author Ceki Gülcü + * @author Ceki Gülcü */ public class NAConverter extends AccessConverter { diff --git a/logback-access/src/main/java/ch/qos/logback/access/pattern/RequestURIConverter.java b/logback-access/src/main/java/ch/qos/logback/access/pattern/RequestURIConverter.java index a66fd18..8118919 100644 --- a/logback-access/src/main/java/ch/qos/logback/access/pattern/RequestURIConverter.java +++ b/logback-access/src/main/java/ch/qos/logback/access/pattern/RequestURIConverter.java @@ -18,7 +18,7 @@ import ch.qos.logback.access.spi.IAccessEvent; /** * The request URI. * - * @author Ceki Gülcü + * @author Ceki Gülcü */ public class RequestURIConverter extends AccessConverter { diff --git a/logback-access/src/main/java/ch/qos/logback/access/pattern/RequestURLConverter.java b/logback-access/src/main/java/ch/qos/logback/access/pattern/RequestURLConverter.java index 473326e..05b7b99 100644 --- a/logback-access/src/main/java/ch/qos/logback/access/pattern/RequestURLConverter.java +++ b/logback-access/src/main/java/ch/qos/logback/access/pattern/RequestURLConverter.java @@ -18,7 +18,7 @@ import ch.qos.logback.access.spi.IAccessEvent; /** * The first line of the request. * - * @author Ceki Gülcü + * @author Ceki Gülcü */ public class RequestURLConverter extends AccessConverter { diff --git a/logback-classic/src/main/java/ch/qos/logback/classic/LoggerContext.java b/logback-classic/src/main/java/ch/qos/logback/classic/LoggerContext.java index c492817..47ca742 100644 --- a/logback-classic/src/main/java/ch/qos/logback/classic/LoggerContext.java +++ b/logback-classic/src/main/java/ch/qos/logback/classic/LoggerContext.java @@ -39,7 +39,7 @@ import ch.qos.logback.core.status.WarnStatus; /** * LoggerContext glues many of the logback-classic components together. In * principle, every logback-classic component instance is attached either - * directly or indirecty to a LoggerContext instance. Just as importantly + * directly or indirectly to a LoggerContext instance. Just as importantly * LoggerContext implements the {@link ILoggerFactory} acting as the * manufacturing source of {@link Logger} instances. * diff --git a/logback-classic/src/main/java/ch/qos/logback/classic/db/package.html b/logback-classic/src/main/java/ch/qos/logback/classic/db/package.html index a696aa0..7bc5610 100644 --- a/logback-classic/src/main/java/ch/qos/logback/classic/db/package.html +++ b/logback-classic/src/main/java/ch/qos/logback/classic/db/package.html @@ -16,7 +16,7 @@ are supported. </p> <p>Just as importantly, the way for obtaining JDBC connections is pluggable. Connections can -be obtained through the tradinal way of DriverManager, or alternatively as a DataSource. +be obtained through the traditional way of DriverManager, or alternatively as a DataSource. A DataSource can be instantiated directly or it can obtained through JNDI. </p> </body> diff --git a/logback-classic/src/main/java/ch/qos/logback/classic/net/SimpleSocketServer.java b/logback-classic/src/main/java/ch/qos/logback/classic/net/SimpleSocketServer.java index 2679c2f..42a0f85 100644 --- a/logback-classic/src/main/java/ch/qos/logback/classic/net/SimpleSocketServer.java +++ b/logback-classic/src/main/java/ch/qos/logback/classic/net/SimpleSocketServer.java @@ -101,7 +101,7 @@ public class SimpleSocketServer extends Thread { } /** - * Signal another thread that we have established a conneciton + * Signal another thread that we have established a connection * This is useful for testing purposes. */ void signalAlmostReadiness() { diff --git a/logback-classic/src/main/java/ch/qos/logback/classic/net/SyslogAppender.java b/logback-classic/src/main/java/ch/qos/logback/classic/net/SyslogAppender.java index 67845db..583033e 100644 --- a/logback-classic/src/main/java/ch/qos/logback/classic/net/SyslogAppender.java +++ b/logback-classic/src/main/java/ch/qos/logback/classic/net/SyslogAppender.java @@ -31,7 +31,7 @@ import ch.qos.logback.core.net.SyslogAppenderBase; * more information about this appender, please refer to the online manual at * http://logback.qos.ch/manual/appenders.html#SyslogAppender * - * @author Ceki Gülcü + * @author Ceki Gülcü */ public class SyslogAppender extends SyslogAppenderBase<ILoggingEvent> { diff --git a/logback-classic/src/main/java/ch/qos/logback/classic/spi/LoggerContextAwareBase.java b/logback-classic/src/main/java/ch/qos/logback/classic/spi/LoggerContextAwareBase.java index b018fa6..4acb929 100644 --- a/logback-classic/src/main/java/ch/qos/logback/classic/spi/LoggerContextAwareBase.java +++ b/logback-classic/src/main/java/ch/qos/logback/classic/spi/LoggerContextAwareBase.java @@ -30,7 +30,7 @@ public class LoggerContextAwareBase extends ContextAwareBase implements LoggerCo public void setContext(Context context) { // check that the context is of type LoggerContext. Otherwise, throw an exception - // Context == null is a degenarate case but nonetheless permitted. + // Context == null is a degenerate case but nonetheless permitted. if(context instanceof LoggerContext || context == null) { super.setContext(context); } else { diff --git a/logback-classic/src/main/java/ch/qos/logback/classic/spi/LoggingEvent.java b/logback-classic/src/main/java/ch/qos/logback/classic/spi/LoggingEvent.java index 8cbf883..b23373d 100644 --- a/logback-classic/src/main/java/ch/qos/logback/classic/spi/LoggingEvent.java +++ b/logback-classic/src/main/java/ch/qos/logback/classic/spi/LoggingEvent.java @@ -66,7 +66,7 @@ public class LoggingEvent implements ILoggingEvent { * Level of logging event. * * <p> - * This field should not be accessed directly. You shoud use the + * This field should not be accessed directly. You should use the * {@link #getLevel} method instead. * </p> * @@ -77,7 +77,7 @@ public class LoggingEvent implements ILoggingEvent { // we gain significant space at serialization time by marking // formattedMessage as transient and constructing it lazily in - // getFormmatedMessage() + // getFormattedMessage() private transient String formattedMessage; private transient Object[] argumentArray; diff --git a/logback-classic/src/main/java/ch/qos/logback/classic/spi/LoggingEventVO.java b/logback-classic/src/main/java/ch/qos/logback/classic/spi/LoggingEventVO.java index d8228d2..26c66a4 100644 --- a/logback-classic/src/main/java/ch/qos/logback/classic/spi/LoggingEventVO.java +++ b/logback-classic/src/main/java/ch/qos/logback/classic/spi/LoggingEventVO.java @@ -48,7 +48,7 @@ public class LoggingEventVO implements ILoggingEvent, Serializable { // we gain significant space at serialization time by marking // formattedMessage as transient and constructing it lazily in - // getFormmatedMessage() + // getFormattedMessage() private transient String formattedMessage; private transient Object[] argumentArray; diff --git a/logback-classic/src/main/java/ch/qos/logback/classic/turbo/MDCFilter.java b/logback-classic/src/main/java/ch/qos/logback/classic/turbo/MDCFilter.java index 111db11..1aed275 100644 --- a/logback-classic/src/main/java/ch/qos/logback/classic/turbo/MDCFilter.java +++ b/logback-classic/src/main/java/ch/qos/logback/classic/turbo/MDCFilter.java @@ -24,7 +24,7 @@ import ch.qos.logback.core.spi.FilterReply; * This class allows output for a given MDC value. * * <p> - * When the given value is identified by this TubroFilter, + * When the given value is identified by this TurboFilter, * the reply is based on the OnMatch option. * The information is taken from the MDC. For this TurboFilter to work, * one must set the key that will be used to diff --git a/logback-classic/src/main/java/ch/qos/logback/classic/turbo/MatchingFilter.java b/logback-classic/src/main/java/ch/qos/logback/classic/turbo/MatchingFilter.java index a4da3a9..09c25c7 100644 --- a/logback-classic/src/main/java/ch/qos/logback/classic/turbo/MatchingFilter.java +++ b/logback-classic/src/main/java/ch/qos/logback/classic/turbo/MatchingFilter.java @@ -17,7 +17,7 @@ import ch.qos.logback.core.spi.FilterReply; /** * An abstract class containing support for {@link #onMatch} on {@link #onMismatch} - * attributes, shared by many but not all tubo filters. + * attributes, shared by many but not all turbo filters. * * @author Ceki Gulcu */ diff --git a/logback-classic/src/main/java/ch/qos/logback/classic/util/ContextSelectorStaticBinder.java b/logback-classic/src/main/java/ch/qos/logback/classic/util/ContextSelectorStaticBinder.java index a2d9a02..fb7247f 100644 --- a/logback-classic/src/main/java/ch/qos/logback/classic/util/ContextSelectorStaticBinder.java +++ b/logback-classic/src/main/java/ch/qos/logback/classic/util/ContextSelectorStaticBinder.java @@ -75,7 +75,7 @@ public class ContextSelectorStaticBinder { } /** - * Intantiate the context selector class designated by the user. The selector + * Instantiate the context selector class designated by the user. The selector * must have a constructor taking a LoggerContext instance as an argument. * * @param defaultLoggerContext diff --git a/logback-classic/src/test/java/ch/qos/logback/classic/net/mock/MockSyslogServer.java b/logback-classic/src/test/java/ch/qos/logback/classic/net/mock/MockSyslogServer.java index b85344b..7757bf5 100644 --- a/logback-classic/src/test/java/ch/qos/logback/classic/net/mock/MockSyslogServer.java +++ b/logback-classic/src/test/java/ch/qos/logback/classic/net/mock/MockSyslogServer.java @@ -20,7 +20,7 @@ import java.util.List; /** * - * @author Ceki Gülcü + * @author Ceki Gülcü */ public class MockSyslogServer extends Thread { diff --git a/logback-core/src/main/java/ch/qos/logback/core/boolex/EvaluationException.java b/logback-core/src/main/java/ch/qos/logback/core/boolex/EvaluationException.java index 621c90a..7af4803 100644 --- a/logback-core/src/main/java/ch/qos/logback/core/boolex/EvaluationException.java +++ b/logback-core/src/main/java/ch/qos/logback/core/boolex/EvaluationException.java @@ -16,7 +16,7 @@ package ch.qos.logback.core.boolex; /** * This exception wraps exceptions thrown while evaluating events. * - * @author Ceki Gülcü + * @author Ceki Gülcü */ public class EvaluationException extends Exception { diff --git a/logback-core/src/main/java/ch/qos/logback/core/db/package.html b/logback-core/src/main/java/ch/qos/logback/core/db/package.html index 213e220..a3ff88d 100644 --- a/logback-core/src/main/java/ch/qos/logback/core/db/package.html +++ b/logback-core/src/main/java/ch/qos/logback/core/db/package.html @@ -15,7 +15,7 @@ are supported. </p> <p>Just as importantly, the way for obtaining JDBC connections is pluggable. Connections can -be obtained through the tradinal way of DriverManager, or alternatively as a DataSource. +be obtained through the traditional way of DriverManager, or alternatively as a DataSource. A DataSource can be instantiated directly or it can obtained through JNDI. </p> </body> diff --git a/logback-core/src/main/java/ch/qos/logback/core/filter/package.html b/logback-core/src/main/java/ch/qos/logback/core/filter/package.html index c757da6..6d5ee0f 100644 --- a/logback-core/src/main/java/ch/qos/logback/core/filter/package.html +++ b/logback-core/src/main/java/ch/qos/logback/core/filter/package.html @@ -7,7 +7,7 @@ <body> - <p>Contains base classes to the event filtering functionnalities of logback.</p> + <p>Contains base classes to the event filtering functionality of logback.</p> </body> </html> \ No newline at end of file diff --git a/logback-core/src/main/java/ch/qos/logback/core/helpers/Transform.java b/logback-core/src/main/java/ch/qos/logback/core/helpers/Transform.java index 3642005..34c32e8 100644 --- a/logback-core/src/main/java/ch/qos/logback/core/helpers/Transform.java +++ b/logback-core/src/main/java/ch/qos/logback/core/helpers/Transform.java @@ -69,7 +69,7 @@ public class Transform { /** - * Ensures that embeded CDEnd strings (]]>) are handled properly within + * Ensures that embedded CDEnd strings (]]>) are handled properly within * message, NDC and throwable tag text. * * @param output diff --git a/logback-core/src/main/java/ch/qos/logback/core/net/JMSAppenderBase.java b/logback-core/src/main/java/ch/qos/logback/core/net/JMSAppenderBase.java index d5d8f90..cc08be4 100644 --- a/logback-core/src/main/java/ch/qos/logback/core/net/JMSAppenderBase.java +++ b/logback-core/src/main/java/ch/qos/logback/core/net/JMSAppenderBase.java @@ -167,7 +167,7 @@ public abstract class JMSAppenderBase<E> extends AppenderBase<E> { } /** - * The paswword to use when creating a topic session. + * The password to use when creating a topic session. */ public void setPassword(String password) { this.password = password; diff --git a/logback-core/src/main/java/ch/qos/logback/core/net/SMTPAppenderBase.java b/logback-core/src/main/java/ch/qos/logback/core/net/SMTPAppenderBase.java index f3bb08c..5e88e59 100644 --- a/logback-core/src/main/java/ch/qos/logback/core/net/SMTPAppenderBase.java +++ b/logback-core/src/main/java/ch/qos/logback/core/net/SMTPAppenderBase.java @@ -92,7 +92,7 @@ public abstract class SMTPAppenderBase<E> extends AppenderBase<E> { private int errorCount = 0; /** - * return a layout for the subjet string as appropriate for the module. If the + * return a layout for the subject string as appropriate for the module. If the * subjectStr parameter is null, then a default value for subjectStr should be * used. * @@ -342,7 +342,7 @@ public abstract class SMTPAppenderBase<E> extends AppenderBase<E> { mimeMsg.setSentDate(new Date()); Transport.send(mimeMsg); } catch (Exception e) { - addError("Error occured while sending e-mail notification.", e); + addError("Error occurred while sending e-mail notification.", e); } } diff --git a/logback-core/src/main/java/ch/qos/logback/core/net/SocketAppenderBase.java b/logback-core/src/main/java/ch/qos/logback/core/net/SocketAppenderBase.java index 6b2fb5c..b77f509 100644 --- a/logback-core/src/main/java/ch/qos/logback/core/net/SocketAppenderBase.java +++ b/logback-core/src/main/java/ch/qos/logback/core/net/SocketAppenderBase.java @@ -263,7 +263,7 @@ public abstract class SocketAppenderBase<E> extends AppenderBase<E> { * * <p> * It stops trying whenever a connection is established. It will restart to - * try reconnect to the server when previpously open connection is droppped. + * try reconnect to the server when previously open connection is dropped. * * @author Ceki Gülcü * @since 0.8.4 diff --git a/logback-core/src/main/java/ch/qos/logback/core/net/SyslogAppenderBase.java b/logback-core/src/main/java/ch/qos/logback/core/net/SyslogAppenderBase.java index d0cf074..64b4e4e 100644 --- a/logback-core/src/main/java/ch/qos/logback/core/net/SyslogAppenderBase.java +++ b/logback-core/src/main/java/ch/qos/logback/core/net/SyslogAppenderBase.java @@ -25,7 +25,7 @@ import ch.qos.logback.core.Layout; /** * Base class for SyslogAppender. * - * @author Ceki Gülcü + * @author Ceki Gülcü * * @param <E> */ @@ -201,7 +201,7 @@ public abstract class SyslogAppenderBase<E> extends AppenderBase<E> { } /** - * The port number on the syslog server to connect to. Nornally, wou would not + * The port number on the syslog server to connect to. Normally, you would not * want to change the default value, that is 514. */ public void setPort(int port) { @@ -233,8 +233,8 @@ public abstract class SyslogAppenderBase<E> extends AppenderBase<E> { } /** - * The <b>suffixPattern</b> option specifies the fortmat of the - * non-standardized part the message sent to the syslog server. + * The <b>suffixPattern</b> option specifies the format of the + * non-standardized part of the message sent to the syslog server. * * @param pattern */ diff --git a/logback-core/src/main/java/ch/qos/logback/core/pattern/FormatInfo.java b/logback-core/src/main/java/ch/qos/logback/core/pattern/FormatInfo.java index 1f6c9a5..bfbd303 100644 --- a/logback-core/src/main/java/ch/qos/logback/core/pattern/FormatInfo.java +++ b/logback-core/src/main/java/ch/qos/logback/core/pattern/FormatInfo.java @@ -45,7 +45,7 @@ public class FormatInfo { * a FormatInfo. * * @param str A String to convert into a FormatInfo object - * @return A newly created and approprioately initialized FormatInfo object. + * @return A newly created and appropriately initialized FormatInfo object. * @throws IllegalArgumentException */ public static FormatInfo valueOf(String str) throws IllegalArgumentException { diff --git a/logback-core/src/main/java/ch/qos/logback/core/pattern/PostCompileProcessor.java b/logback-core/src/main/java/ch/qos/logback/core/pattern/PostCompileProcessor.java index a61ca2e..128a3df 100644 --- a/logback-core/src/main/java/ch/qos/logback/core/pattern/PostCompileProcessor.java +++ b/logback-core/src/main/java/ch/qos/logback/core/pattern/PostCompileProcessor.java @@ -17,7 +17,7 @@ package ch.qos.logback.core.pattern; /** * Implements this to perform post compile processing for a PatternLayout. * - * For example, PatternLayot in the classic module should add a converter for + * For example, PatternLayout in the classic module should add a converter for * exception handling (otherwise exceptions would not be printed). * * @author Ceki Gulcu diff --git a/logback-core/src/main/java/ch/qos/logback/core/spi/ContextAwareBase.java b/logback-core/src/main/java/ch/qos/logback/core/spi/ContextAwareBase.java index 874a03d..b0814ac 100644 --- a/logback-core/src/main/java/ch/qos/logback/core/spi/ContextAwareBase.java +++ b/logback-core/src/main/java/ch/qos/logback/core/spi/ContextAwareBase.java @@ -24,7 +24,7 @@ import ch.qos.logback.core.status.WarnStatus; * A helper class that implements ContextAware methods. A class can implement * the ContextAware interface by deriving from this class. * - * @author Ceki Gülcü + * @author Ceki Gülcü */ public class ContextAwareBase implements ContextAware { private int noContextWarning = 0; diff --git a/logback-core/src/main/java/ch/qos/logback/core/spi/ContextAwareImpl.java b/logback-core/src/main/java/ch/qos/logback/core/spi/ContextAwareImpl.java index 9512dd1..91d3e93 100644 --- a/logback-core/src/main/java/ch/qos/logback/core/spi/ContextAwareImpl.java +++ b/logback-core/src/main/java/ch/qos/logback/core/spi/ContextAwareImpl.java @@ -25,7 +25,7 @@ import ch.qos.logback.core.status.WarnStatus; * A helper class that implements ContextAware methods. Use this class to * implement the ContextAware interface by composition. * - * @author Ceki Gülcü + * @author Ceki Gülcü */ public class ContextAwareImpl implements ContextAware { diff --git a/logback-core/src/test/java/ch/qos/logback/core/rolling/FileOpener.java b/logback-core/src/test/java/ch/qos/logback/core/rolling/FileOpener.java index 66f8313..6e91093 100644 --- a/logback-core/src/test/java/ch/qos/logback/core/rolling/FileOpener.java +++ b/logback-core/src/test/java/ch/qos/logback/core/rolling/FileOpener.java @@ -20,7 +20,7 @@ import java.io.InputStream; /** * Keep the file "output/test.log open for 10 seconds so that we can test * RollingFileAppender's ability to roll file open by another process. - * @author Ceki Gülcü + * @author Ceki Gülcü */ public class FileOpener { public static void main(String[] args) throws Exception { diff --git a/logback-site/src/site/pages/access.html b/logback-site/src/site/pages/access.html index 8fd3720..057d8c9 100644 --- a/logback-site/src/site/pages/access.html +++ b/logback-site/src/site/pages/access.html @@ -42,7 +42,7 @@ and can thus provide much of the functionality of logback-classic but in the scope of HTPP-access logging. </p> - <p>It should be noted that while loback-access requires + <p>It should be noted that while logback-access requires logback-core, it is independent of logback-classic as well as slf4j. Just as importantly, logback-access artifact must be installed at the container level, not at web-applcation level. It diff --git a/logback-site/src/site/pages/codes.html b/logback-site/src/site/pages/codes.html index 88894ac..29537e5 100644 --- a/logback-site/src/site/pages/codes.html +++ b/logback-site/src/site/pages/codes.html @@ -136,7 +136,7 @@ which are only possible using encoders. <b>During a transition period, layouts passed as parameter will be automatically wrapped by an encoder so that configuration files in the old format (using a - layout instead of encoder) will continue to work unmodifed.</b> + layout instead of encoder) will continue to work unmodified.</b> </p> <hr/> @@ -433,7 +433,7 @@ <p>Given that <code>FixedWindowRollingPolicy</code> performs multiple file rename operations during roll over, and that these operations cannot be guaranteed to be safe in a multi-JVM context, - prudent mode is not allowed in conjuction with a + prudent mode is not allowed in conjunction with a <code>FixedWindowRollingPolicy</code>. </p> diff --git a/logback-site/src/site/pages/consolePlugin.html b/logback-site/src/site/pages/consolePlugin.html index aa66d1b..750dff4 100644 --- a/logback-site/src/site/pages/consolePlugin.html +++ b/logback-site/src/site/pages/consolePlugin.html @@ -233,7 +233,7 @@ <p> The logback plugin lets you filter logging events when they are received. It uses the powerful <code>EvaluatorFilter</code> objects - that are available in logback. For detailled information about these filters, you might want + that are available in logback. For detailed information about these filters, you might want to check the <a href="manual/filters.html">corresponding documentation</a> in the logback manual. In this document, we will only cover some basic points, enough to get you started using the filtering diff --git a/logback-site/src/site/pages/demo.html b/logback-site/src/site/pages/demo.html index 90d7de3..89cec1c 100644 --- a/logback-site/src/site/pages/demo.html +++ b/logback-site/src/site/pages/demo.html @@ -34,7 +34,7 @@ <p class="source">git clone http://git.qos.ch/logback-demo/ logback-demo</p> - <p>This will retreive a copy of the logback demonstration + <p>This will retrieve a copy of the logback demonstration web-application to a directory called <em>logback-demo</em>. The logback demo can be packaged as a <em>war</em> file and deployed to an application server. We strongly recommend the use of <a @@ -74,7 +74,7 @@ <p>We highly encourage you to study the <em>logback.xml</em> configuration file located under the <em>src/main/resources/</em> folder. You might want to keep this file open in an editor window, - since we will modify its contents thoughout the demo. + since we will modify its contents throughout the demo. </p> <p>Let us now visit the <em>ViewStatii</em> page, via the navigation @@ -170,7 +170,7 @@ behaviour once the expression matched (evaluated to true). </p> - <p>After a restart, the <em>Vew logs</em> page will shows the + <p>After a restart, the <em>View logs</em> page will shows the <em>Howdydy-diddly-ho</em> logs, but only for the first 20 seconds. If you wish to see new logging events to be shown on the "View logs" page, then visit the "Prime number" page. diff --git a/logback-site/src/site/pages/documentation.html b/logback-site/src/site/pages/documentation.html index 5c07e09..cb27a5f 100644 --- a/logback-site/src/site/pages/documentation.html +++ b/logback-site/src/site/pages/documentation.html @@ -22,7 +22,7 @@ <h2>Logback documentation</h2> - <p>Below is a list of logback-related documentaiton currently + <p>Below is a list of logback-related documentation currently available.</p> <ul> diff --git a/logback-site/src/site/pages/faq.html b/logback-site/src/site/pages/faq.html index 195f83e..aa80d9c 100644 --- a/logback-site/src/site/pages/faq.html +++ b/logback-site/src/site/pages/faq.html @@ -70,7 +70,7 @@ <li> <a href="#setup_jetty">How can Jetty be instructed to use - logback-classic as its logging implementataion? + logback-classic as its logging implementation? </a> </li> </ol> @@ -187,7 +187,7 @@ <dd> <p>Yes. A logback logger <em>is</em> an SLF4J logger and SLF4J loggers are serializable. This means that an object - referencing a logger will be alble to log after its + referencing a logger will be able to log after its deserialization. </p> @@ -264,7 +264,7 @@ <dd> <p>Logback does not allow logging to be disabled from the command line. However, if the configuration file allows it, you can - set the level of logers on the command line via a Java + set the level of loggers on the command line via a Java system property. Here is such a configuration file.</p> <p class="source"><configuration> diff --git a/logback-site/src/site/pages/manual/appenders.html b/logback-site/src/site/pages/manual/appenders.html index e7d6d4a..f384485 100644 --- a/logback-site/src/site/pages/manual/appenders.html +++ b/logback-site/src/site/pages/manual/appenders.html @@ -993,7 +993,7 @@ public interface RollingPolicy extends LifeCycle { class="option">fileNamePattern</span>. By leaving the <span class="option">file</span> option unset you can avoid file <a href="../codes.html#renamingError">renaming errors</a> which occur - while there exist external file handles refrencing log files during + while there exist external file handles referencing log files during roll over. </p> @@ -2355,7 +2355,7 @@ logger.error(<b>notifyAdmin</b>, href="#smtpDiscriminator">SMTPAppender with MDCDiscriminator</a></h3> - <p>As mentioned earlier, by specifiying a discriminator other than + <p>As mentioned earlier, by specifying a discriminator other than the default one, <code>SMTPAppender</code> will generate email messages containing events pertaining to a particular user, user session or client IP address, depending on the specified discriminator. @@ -2406,7 +2406,7 @@ logger.error(<b>notifyAdmin</b>, <h4><a name= "bufferManagement" href="#bufferManagement">On buffer management in very busy systems</a></h4> - <p>Internally, each distinct value returned by the disciminator + <p>Internally, each distinct value returned by the discriminator will cause the creation of a new cyclic buffer. However, at most <span class="option">maxNumberOfBuffers</span> (by default 64) will be maintained. Whenever the number of buffers rises above @@ -2437,7 +2437,7 @@ logger.error(<b>notifyAdmin</b>, 512 or 1024 without risking running out of memory. </p> - <p>Thuse reare three distinct but complementary mechanisms working + <p>There are three distinct but complementary mechanisms working together to manage cyclic buffers. They ensure that only relevant buffers are kept alive at any given moment, even in very busy systems.</p> @@ -3576,7 +3576,7 @@ public class CountingConsoleAppender extends AppenderBase<ILoggingEvent> { class="option">defaultValue</span> property is used. </p> - <p>The desginated AccessEvent field can be one of COOKIE, + <p>The designated AccessEvent field can be one of COOKIE, REQUEST_ATTRIBUTE, SESSION_ATTRIBUTE, REMOTE_ADDRESS, LOCAL_PORT, REQUEST_URI. Note that the first three fields require that the <span class="option">AdditionalKey</span> property also be @@ -3609,7 +3609,7 @@ public class CountingConsoleAppender extends AppenderBase<ILoggingEvent> { <p>In the above configuration file, a <code>SiftingAppender</code> nests <code>FileAppender</code> instances. The key "id" is - designated as a variable which will be availabe to the nested + designated as a variable which will be available to the nested <code>FileAppender</code> instances. The default discriminator, namely <code>AccessEventDiscriminator</code>, will search for a "username" session attribute in each <code>AccessEvent</code>. If diff --git a/logback-site/src/site/pages/manual/architecture.html b/logback-site/src/site/pages/manual/architecture.html index 9a3f956..7bfa4f5 100644 --- a/logback-site/src/site/pages/manual/architecture.html +++ b/logback-site/src/site/pages/manual/architecture.html @@ -732,7 +732,7 @@ logger.debug("The new entry is {}.", entry);</pre> <pre class="prettyprint source">logger.debug("The new entry is {}. It replaces {}.", entry, oldEntry);</pre> <p>If three or more arguments need to be passed, an - <code>Object[]</code> variant is also availalble. For example, you + <code>Object[]</code> variant is also available. For example, you can write: </p> diff --git a/logback-site/src/site/pages/manual/configuration.html b/logback-site/src/site/pages/manual/configuration.html index 38a8de0..f3ae3d0 100644 --- a/logback-site/src/site/pages/manual/configuration.html +++ b/logback-site/src/site/pages/manual/configuration.html @@ -381,7 +381,7 @@ public class Foo { <p>It is strongly recommended to register a status listener, e.g. <code>OnConsoleStatusListener</code>, so that problems - occuring during the lifetime of your application, well after + occurring during the lifetime of your application, well after logback is initialized, can be reported. See the section on <a href="#statusListener">status listeners</a> further below.</p> @@ -1405,7 +1405,7 @@ public class MyApp3 { <h4>Nested variable substitution</h4> - <p>Nested variable subsitution is also supported. By nested, we + <p>Nested variable substitution is also supported. By nested, we mean that the value definition of a variable contains references to other variables. Suppose you wish to use variables to specify not only the destination directory but also the file name, and combine @@ -1755,7 +1755,7 @@ fileName=myApp.log .... </configuration></pre> - <p>Setting the <span class="option">resetJUL</span> propery of + <p>Setting the <span class="option">resetJUL</span> property of LevelChangePropagator will reset all previous level configurations of all j.u.l. loggers. However, previously installed handlers will be left untouched.</p> diff --git a/logback-site/src/site/pages/manual/filters.html b/logback-site/src/site/pages/manual/filters.html index 0d9e9dd..28001b3 100644 --- a/logback-site/src/site/pages/manual/filters.html +++ b/logback-site/src/site/pages/manual/filters.html @@ -126,8 +126,8 @@ public class SampleFilter extends Filter>ILoggingEvent> { } }</pre> - <p>The configutation files shown next attaches a - <code>SampleFilter</code> to a <code>ConsoleAppener</code>. + <p>The configuration files shown next attaches a + <code>SampleFilter</code> to a <code>ConsoleAppender</code>. </p> <em>Example: SampleFilter configuration @@ -151,7 +151,7 @@ public class SampleFilter extends Filter>ILoggingEvent> { </configuration></pre> <p>With the help of Joran, logback's configuration framework, - specifying properties or sub-componenets to filters is also + specifying properties or sub-components to filters is also easy. After adding the corresponding setter method in the filter class, specify the value of the property in an xml element named after the property, nesting it within a <code><filter></code> @@ -282,7 +282,7 @@ public class SampleFilter extends Filter>ILoggingEvent> { filtering. <code>GEventEvaluator</code> requires the Groovy runtime. Please see the <a href="../setup.html#gEventEvaluator">corresponding section</a> of - the setup document on adding the Groovy runtinme to your class + the setup document on adding the Groovy runtime to your class path. </p> @@ -384,7 +384,7 @@ public class SampleFilter extends Filter>ILoggingEvent> { <p>Evaluation expressions are compiled on-the-fly during the interpretation of the configuration file. As a user, you do not need to worry about the actual plumbing. However, it is your - reponsibility to ensure that the Java language expression returns + responsibility to ensure that the Java language expression returns a boolean, i.e. that it evaluates to true or false. </p> @@ -422,7 +422,7 @@ public class SampleFilter extends Filter>ILoggingEvent> { message.</td> </tr> <tr> - <td>formatedMessage</td> + <td>formattedMessage</td> <td><code>String</code></td> <td>The formatted message in the logging request. For some logger <em>l</em>, when you write l.info("Hello {}", name); @@ -501,7 +501,7 @@ public class SampleFilter extends Filter>ILoggingEvent> { value of the "throwable" variable will be null. Unfortunately, "throwable" does not survive serialization. Thus, on remote systems, its value will always be null. For location - independent expresisons, use the <code>throwableProxy</code> + independent expressions, use the <code>throwableProxy</code> variable described next. </td> </tr> @@ -572,7 +572,7 @@ public class SampleFilter extends Filter>ILoggingEvent> { <p>Given that the <span class="option">OnMismatch</span> property is set to NEUTRAL and the <span class="option">OnMatch</span> - property set to DENY, this evalutor filter will drop all logging + property set to DENY, this evaluator filter will drop all logging events whose message contains the string "billing". </p> @@ -1113,7 +1113,7 @@ logger.debug("Hello {}.", name1);</pre> href="../xref/ch/qos/logback/access/boolex/JaninoEventEvaluator.html">JaninoEventEvaluator</a>. It takes arbitrary Java language boolean expressions as the evaluation criteria. We refer to such Java language blocks as - "<em>evaluation expresisons</em>". Evaluation expressions enable + "<em>evaluation expressions</em>". Evaluation expressions enable great flexibility in event filtering. <code>JaninoEventEvaluator</code> requires the <a href="http://docs.codehaus.org/display/JANINO/Home">Janino @@ -1125,7 +1125,7 @@ logger.debug("Hello {}.", name1);</pre> <p>Evaluation expressions are compiled on-the-fly during the interpretation of the configuration file. As a user, you do not need to worry about the actual plumbing. However, it is your - reponsibility to ensure that the Java language expression returns + responsibility to ensure that the Java language expression returns a boolean, i.e. that it evaluates to true or false. </p> diff --git a/logback-site/src/site/pages/manual/groovy.html b/logback-site/src/site/pages/manual/groovy.html index 7dd8513..a3443c6 100644 --- a/logback-site/src/site/pages/manual/groovy.html +++ b/logback-site/src/site/pages/manual/groovy.html @@ -70,7 +70,7 @@ programs. And since Groovy is a super-set of Java, whatever configuration actions you can perform in Java, you can do the same within a <em>logback.groovy</em> file. However, since configuring - logback progammatically using Java syntax can be cumbersome, we + logback programmatically using Java syntax can be cumbersome, we added a few logback-specific extensions to make your life easier. We try hard to limit the number of logback-specific syntactic extensions to an absolute minimum. If you are already diff --git a/logback-site/src/site/pages/manual/introduction.html b/logback-site/src/site/pages/manual/introduction.html index 287fb5a..2a0faba 100644 --- a/logback-site/src/site/pages/manual/introduction.html +++ b/logback-site/src/site/pages/manual/introduction.html @@ -137,7 +137,7 @@ public class HelloWorld1 { <p class="source">20:49:07.962 [main] DEBUG chapters.introduction.HelloWorld1 - Hello world.</p> <p>Logback can report information about its internal state using a - built-in status system. Important events occuring during logback's + built-in status system. Important events occurring during logback's lifetime can be accessed through a component called <code>StatusManager</code>. For the time being, let us instruct logback to print its internal state by invoking the static diff --git a/logback-site/src/site/pages/manual/layouts.html b/logback-site/src/site/pages/manual/layouts.html index 95de04c..6d55557 100644 --- a/logback-site/src/site/pages/manual/layouts.html +++ b/logback-site/src/site/pages/manual/layouts.html @@ -60,7 +60,7 @@ String getContentType(); }</pre> - <p>This interface is rather simple and yet is sufficent for many + <p>This interface is rather simple and yet is sufficient for many formatting needs. The Texan developer from Texas, whom you might know from Joseph Heller's <em>Catch-22</em>, might exclaim: it just takes five methods to implement a layout!!? @@ -919,7 +919,7 @@ Caller+2 at mainPackage.ConfigTester.main(ConfigTester.java:38)</pre> <p>Logback goes to great lengths to ensure that the class packaging information it displays is correct, even in - arbirarily complex class loader hierarchies. However, when + arbitrarily complex class loader hierarchies. However, when it is unable to guarantee the absolute correctness of the information, then it will prefix the data with a tilde, i.e. the '~' character. Thus, it is theoretically possible for @@ -950,7 +950,7 @@ Caller+2 at mainPackage.ConfigTester.main(ConfigTester.java:38)</pre> </td> <td> - <p>Altough it <em>pretends</em> to handle stack trace data, + <p>Although it <em>pretends</em> to handle stack trace data, this conversion word does not output any data, thus, effectively ignoring exceptions. </p> @@ -1338,7 +1338,7 @@ Caller+2 at mainPackage.ConfigTester.main(ConfigTester.java:38)</pre> are presented in a <a href="filters.html#evalutatorFilter">dedicated section of the chapter on filters</a> which you MUST read if you want to use - evaluators in any meaninful way. Also note that the examples below + evaluators in any meaningful way. Also note that the examples below are implicitly based on <code>JaninoEventEvaluator</code> which requires the <a href="http://docs.codehaus.org/display/JANINO/Home">Janino @@ -1425,7 +1425,7 @@ public class CallerEvaluatorExample { <p>The above application does nothing particularly fancy. Five logging requests are issued, the third one emitting the message - "who calls theee?" + "who calls thee?" </p> <p>The command</p> @@ -1464,7 +1464,7 @@ Caller+0 at chapters.layouts.CallerEvaluatorExample.main(CallerEvaluatorExampl <p>Let us consider at a different situation. When exceptions are included in a logging request, their stack trace is also - output. However, one might want to supress the stack trace for + output. However, one might want to suppress the stack trace for some specific exceptions. </p> @@ -1521,7 +1521,7 @@ public class ExceptionEvaluatorExample { <p>In the next configuration file, the evaluation expression matches events containing a throwable of type <code>chapters.layouts.TextException</code>, precisely the type of - exceptions we wish to supress. + exceptions we wish to suppress. </p> <em> @@ -1764,7 +1764,7 @@ public class MySampleConverter extends ClassicConverter { <p>The <a href="../xref/chapters/layouts/TrivialMain.html">TrivialMain</a> application logs a few messages finishing with an exception. The - commmand:</p> + command:</p> <p class="source">java chapters.layouts.TrivialMain src/main/java/chapters/layouts/htmlLayoutConfig1.xml</p> @@ -1895,7 +1895,7 @@ public class MySampleConverter extends ClassicConverter { <code>PatternLayout</code></a> in logback-access can be configured in much the same way as its classic counterpart. However it features additional conversion specifiers suited for logging - particular bits of information availalbe only in HTTP servlet + particular bits of information available only in HTTP servlet requests and HTTP servlet responses. </p> @@ -2118,7 +2118,7 @@ public class MySampleConverter extends ClassicConverter { <code>HttpServletResponse</code> by a <a href="../xref/ch/qos/logback/access/servlet/TeeHttpServletResponse.html"> <code>TeeHttpServletResponse</code></a>. The latter object - allows access to the requet's <code>InputStream</code> + allows access to the request's <code>InputStream</code> multiple times without any loss of data. </p> </td> @@ -2127,7 +2127,7 @@ public class MySampleConverter extends ClassicConverter { <td align="center"><b>fullResponse</b></td> <td> <p>This conversion word takes all the available data - associated with the response, inclusing all headers of the + associated with the response, including all headers of the response and response contents. </p> </td> @@ -2190,7 +2190,7 @@ public class MySampleConverter extends ClassicConverter { <p>What can be better than a real world example? Our own log4j properties for logback <a href="http://logback.qos.ch/translator/">translator</a> makes use - of logback-access to demonstrate live ouput from + of logback-access to demonstrate live output from <code>RollingFileAppender</code> with <code>HTMLLayout</code>.</p> diff --git a/logback-site/src/site/pages/manual/mdc.html b/logback-site/src/site/pages/manual/mdc.html index 5522b3d..2977d96 100644 --- a/logback-site/src/site/pages/manual/mdc.html +++ b/logback-site/src/site/pages/manual/mdc.html @@ -318,7 +318,7 @@ public class NumberCruncherServer extends UnicastRemoteObject } // Placing artificial delays in tight loops will also lead to - // sub-optimal resuts. :-) + // sub-optimal results. :-) delay(100); } @@ -730,7 +730,7 @@ public class UserServletFilter implements Filter { <p>Once the filter is installed, values corresponding to each MDC key will be output by the %X <a - href="layouts.html#conversionWord">conversion word</a> acoording to + href="layouts.html#conversionWord">conversion word</a> according to the key passes as first option. For example, to print the remote host followed by the request URI on one line, the date followed by the message on the next, you would set <code>PatternLayout</code>'s diff --git a/logback-site/src/site/pages/manual/migrationFromLog4j.html b/logback-site/src/site/pages/manual/migrationFromLog4j.html index 15e6727..22bcda5 100644 --- a/logback-site/src/site/pages/manual/migrationFromLog4j.html +++ b/logback-site/src/site/pages/manual/migrationFromLog4j.html @@ -124,9 +124,9 @@ public class TrivialLogbackLayout extends <b>LayoutBase<ILoggingEvent></b> { <code>activateOptions</code>() method invoked by log4j configurators, that is <code>PropertyConfigurator</code> or <code>DOMConfigurator</code> just after all the options of the - layout have been set. Thus, the layout will have an oppurtunity to + layout have been set. Thus, the layout will have an opportunity to check that its options are coherent and if so, proceed to fully - intialize itself.</p> + initialize itself.</p> <p>In logback-classic, layouts must implement the <a diff --git a/logback-site/src/site/pages/manual/onJoran.html b/logback-site/src/site/pages/manual/onJoran.html index 2c6d5be..7a78fbe 100644 --- a/logback-site/src/site/pages/manual/onJoran.html +++ b/logback-site/src/site/pages/manual/onJoran.html @@ -40,7 +40,7 @@ </p> <p>Joran is actually a generic configuration system which can be - used independently of logging. To emphaises this point, we should + used independently of logging. To emphasize this point, we should mention that the logback-core module does not have a notion of loggers. In that spirit, most of the examples in this chapter have nothing to do with loggers, appenders or layouts. @@ -131,7 +131,7 @@ migrated to SAX in order to benefit from element location information, available only with the SAX API. Location information allows Joran to display the exact line and column number where an - error occured, which comes in very handy in indentifying parsing + error occurred, which comes in very handy in identifying parsing problems. </p> @@ -225,7 +225,7 @@ public abstract class Action { processes SAX events. </p> <p>When several rules match the current pattern, then exact - matches override suffix matches, and suffix matches overide prefix + matches override suffix matches, and suffix matches override prefix matches. For exact details of the implementation, please see the <a href="../xref/ch/qos/logback/core/joran/spi/SimpleRuleStore.html">SimpleRuleStore</a> class. @@ -294,7 +294,7 @@ public abstract class Action { <p class="command">java chapters.onJoran.helloWorld.HelloWorld src/main/java/chapters/onJoran/helloWorld/hello.xml</p> - <p>You are highly encourared to poke about in this example, by adding + <p>You are highly encouraged to poke about in this example, by adding new rules on the rule store, modifying the XML document (hello.xml) and adding new actions. </p> diff --git a/logback-site/src/site/pages/news.html b/logback-site/src/site/pages/news.html index 928f35b..a4f41e6 100644 --- a/logback-site/src/site/pages/news.html +++ b/logback-site/src/site/pages/news.html @@ -32,7 +32,7 @@ <p>Fixed <a href="http://jira.qos.ch/browse/LBCLASSIC-254">LBCLASSIC-254</a>, - a performace issue in <code>LogbackMDCAdapter</code> as reported + a performance issue in <code>LogbackMDCAdapter</code> as reported by Michael Franz.</p> <p>Given that events reference a snapshot of the current MDC map, @@ -43,14 +43,14 @@ to fix LBCLASSIC-254</p>. <p><code>ConfigurationWatchList</code> no longer emits an error - message when it encouters a configuraton file placed in a jar + message when it encounters a configuration file placed in a jar file, fixing <a href="http://jira.qos.ch/browse/LBCLASSIC-246">LBCLASSIC-246</a> as reported by Joern Huxhorn. </p> <p>Logback now emits a clearer error message in case a conversion - pattern misses a closing parenthesis or if an openening + pattern misses a closing parenthesis or if an opening parenthesis is misplaced. This fixes <a href="http://jira.qos.ch/browse/LBCORE-193">LBCORE-193</a> reported by B. K. Oxley.</p> @@ -78,7 +78,7 @@ <p>In the <a href="apidocs/ch/qos/logback/core/Context.html">Context</a> interface, the previously misspelled property - <code>bithTime</code> ia now renamed as + <code>bithTime</code> is now renamed as <code>birthTime</code>. This is a backward-incompatible change. All pre-existing references to "bithTime" property now need to referenced as "birthTime".</p> @@ -204,7 +204,7 @@ <p>As reported in <a href="http://jira.qos.ch/browse/LBCORE-164">LBCORE-164</a>, <code>SizeAndTimeBasedFNATP</code> would cause previous logging - files with indexes over nine to be overwitten on application + files with indexes over nine to be overwritten on application restart. This complex bug was reported and precisely diagnosed by Dieter Mueller. He has also proposed a fix which was subsequently adopted as is.</p> @@ -218,7 +218,7 @@ null.</p> <p>Fixed issue with <code>SizeAndTimeBasedFNATP</code> in presence - of application stop/restart and non-null file proprety. This issue + of application stop/restart and non-null file property. This issue was reported by Tom Liu in <a href="http://jira.qos.ch/browse/LBCORE-131">LBCORE-131</a>.</p> @@ -279,7 +279,7 @@ which processes boolean expression written in the Groovy language. </p> - <p>Fixed rollover problem occuring when the target directory was + <p>Fixed rollover problem occurring when the target directory was missing as reported in <a href="http://jira.qos.ch/browse/LBCORE-151">LBCORE-151</a> by Torsten Juergeleit. A closely related problem was reported in <a @@ -350,7 +350,7 @@ encoders. <b>During a transition period, layouts passed as parameter will be automatically wrapped by an encoder so that configuration files in the old format (using a layout instead of - encoder) will continue to work unmodifed.</b> + encoder) will continue to work unmodified.</b> </p> </div> @@ -422,7 +422,7 @@ ALTER TABLE logging_event ADD arg3 VARCHAR(254);</pre> <p>Request header names in AccessEvent (logback-access) are now stored in a case insensitive way as specified in RFC 2616. This prevents compatibility issues, in particular with recent versions - of Tomcat whcih store request header names in lower-case.</p> + of Tomcat which store request header names in lower-case.</p> <p>Fixed <a @@ -517,10 +517,10 @@ ALTER TABLE logging_event ADD arg3 VARCHAR(254);</pre> href="http://jira.qos.ch/browse/LBCLASSIC-165">LBCLASSIC-165</a> and <a href="http://jira.qos.ch/browse/LBCLASSIC-121">LBCLASSIC-121</a> - by applying the relavant patches supplied by Hugues Malphettes. + by applying the relevant patches supplied by Hugues Malphettes. </p> - <p>Made the OSGi import declerations for Janino and javax optional + <p>Made the OSGi import declarations for Janino and javax optional as proposed by David Varnes in <a href="http://jira.qos.ch/browse/LBCORE-101">LBCORE-101</a>.</p> @@ -565,7 +565,7 @@ ALTER TABLE logging_event ADD arg3 VARCHAR(254);</pre> <p>When a logger is named after an inner class, the '$' is used as a separator, instead of the usual '.'. This fixes the level - inheritence issue described in <a + inheritance issue described in <a href="http://jira.qos.ch/browse/LBCLASSIC-102">LBCLASSIC-102</a> and as reported by Joern Huxhorn.</p> @@ -617,7 +617,7 @@ ALTER TABLE logging_event ADD arg3 VARCHAR(254);</pre> <p>The <code>TimeBasedTriggeringPolicy</code> has been heavily - refactored. It is now possible to trigger rolling simultaenously + refactored. It is now possible to trigger rolling simultaneously by <a href="manual/appenders.html#SizeAndTimeBasedFNATP">time and by size</a>, fixing <a href="http://jira.qos.ch/browse/LBCORE-61">LBCORE-61</a>. @@ -744,7 +744,7 @@ ALTER TABLE logging_event ADD arg3 VARCHAR(254);</pre> and the other for <a href="access.html#viewingStatusMessages">logback-access</a>.</p> - <p>Added the <code>clear()</code> mthod to the + <p>Added the <code>clear()</code> method to the <code>StatusManager</code> interface. After reconfiguration, it may be desirable to clear the status list maintained by a <code>StatusManager</code>. This change was requested by Alexis @@ -917,7 +917,7 @@ ALTER TABLE logging_event ADD arg3 VARCHAR(254);</pre> <code>NullPointerException</code> would be thrown. </p> - <p>In reponse to <a + <p>In response to <a href="http://jira.qos.ch/browse/LBCLASSIC-61">LBCLASSIC-61</a>, <a href="http://jira.qos.ch/browse/LBCLASSIC-33">LBCLASSIC-33</a>, <a href="http://jira.qos.ch/browse/LBCLASSIC-14">LBCLASSIC-24</a> and @@ -928,7 +928,7 @@ ALTER TABLE logging_event ADD arg3 VARCHAR(254);</pre> <p>Fixed <a href="http://jira.qos.ch/browse/LBGENERAL-22">LBGENERAL-22</a>. The <a href="http://logback.qos.ch/translator/">log4j.properties - translator</a> web-application has been significatnly refactored. + translator</a> web-application has been significantly refactored. </p> <p>Fixed improvement request <a @@ -1002,7 +1002,7 @@ ALTER TABLE logging_event ADD arg3 VARCHAR(254);</pre> <p>Fixed <a href="http://jira.qos.ch/browse/LBCLASSIC-77">LBCLASSIC-77</a> - reported independenly by Gianni Doe, Yannick Haudry and Yossi Shaul. + reported independently by Gianni Doe, Yannick Haudry and Yossi Shaul. The childValue() method of <code>CopyOnInheritThreadLocal</code> class part of MDC code no longer throws a <code>NullPointerException</code>. @@ -1020,13 +1020,13 @@ ALTER TABLE logging_event ADD arg3 VARCHAR(254);</pre> <p>The LogbackValve in logback-access (ensuring integration with Tomcat), will now systematically print its internal status upon initialization, unless told to be quiet. This greatly helps - troubleshooting the configration of logback-access under Tomcat. + troubleshooting the configuration of logback-access under Tomcat. </p> <p>Fixed <a href="http://bugzilla.qos.ch/show_bug.cgi?id=147">bug - 147</a> which occured when the user inadvertently attempted to set + 147</a> which occurred when the user inadvertently attempted to set the layout of a <code>SyslogAppender</code>. The code now actively - prevents this. Documenation has been updated to reflect the change. + prevents this. Documentation has been updated to reflect the change. </p> <p>Fixed <a href="http://jira.qos.ch/browse/LBCLASSIC-56">bug @@ -1038,7 +1038,7 @@ ALTER TABLE logging_event ADD arg3 VARCHAR(254);</pre> href="http://svn.qos.ch/viewvc?view=rev&revision=1678">now cleared</a> when the <code>reset</code>() method is called. This problem was reported on May 1st, 2008, by Julia Hu on the logback - developpers list. + developers list. </p> <!-- ========================== LB CORE ================== --> @@ -1048,7 +1048,7 @@ ALTER TABLE logging_event ADD arg3 VARCHAR(254);</pre> rollover, compression of large files would bring all logging to a halt. In this latest release, the rolled over file is first renamed, which is a relatively fast operation, and only then is the renamed - file compressed asyncronously (in a separate thread). + file compressed asynchronously (in a separate thread). </p> <p>Fixed issue <a @@ -1118,8 +1118,8 @@ ALTER TABLE logging_event ADD arg3 VARCHAR(254);</pre> <p>Fixed issue <a href="http://jira.qos.ch/browse/LBCLASSIC-68">LBCLASSIC-68</a> reported by Gili Tzabari. In environments where the TCCL (Thread - Context Class Laoder) was not set, logback was unable to located its - default configuraiton files. Logback now uses the class loader that + Context Class Loader) was not set, logback was unable to located its + default configuration files. Logback now uses the class loader that loaded logback itself to locate its resources instead of the TCCL. This approach is simpler and deemed to cover more environments, i.e. more widely applicable. @@ -1141,7 +1141,7 @@ ALTER TABLE logging_event ADD arg3 VARCHAR(254);</pre> </p> <p>Added a new TurboFilter called DynamicThresholdFilter which can - filter events depending on MDC values based on a variery of criteria + filter events depending on MDC values based on a variety of criteria such as company name, product or the end user. This filter was contributed by Ralph Goers in <a href="http://jira.qos.ch/browse/LBCLASSIC-53">LBCLASSIC-53</a>. @@ -1160,8 +1160,8 @@ ALTER TABLE logging_event ADD arg3 VARCHAR(254);</pre> 64</a> and independently by Peter Huber. </p> - <p>Logback no longer includes retro-weaver generted jars for JDK - 1.4. There seemes to be little interest in JDK 1.4 builds. Calling + <p>Logback no longer includes retro-weaver generated jars for JDK + 1.4. There seems to be little interest in JDK 1.4 builds. Calling retro-weaver increases logback's build time by a few seconds each time – seconds in which we can do more productive things. </p> @@ -1220,7 +1220,7 @@ ALTER TABLE logging_event ADD arg3 VARCHAR(254);</pre> <p>Fixed <a href="http://bugzilla.qos.ch/show_bug.cgi?id=52">bug 52</a> reported by Kenichi Masuko. The bug has been fixed on March 8th, 2007. Starting with this release, Joran will support the - injection of any enum tpye, not just <code>FilterReply</code>. + injection of any enum type, not just <code>FilterReply</code>. </p> <hr width="80%" align="center" /> @@ -1330,7 +1330,7 @@ ALTER TABLE logging_event ADD arg3 VARCHAR(254);</pre> automatic initialization, it makes better sense to first check for <em>logback-test.xml</em> file and only if that fails, to check for <em>logback.xml</em>. Maven2 will guarantee that the - logback-test.xml file, if places undder test/resources will not be + logback-test.xml file, if places under test/resources will not be included in the artifact it produces. </p> @@ -1349,7 +1349,7 @@ ALTER TABLE logging_event ADD arg3 VARCHAR(254);</pre> </p> <p>The logback team released today the first version of a plugin for - Eclipse that allows developpers to visualize logs generated by a + Eclipse that allows developers to visualize logs generated by a running application. It offers several nice features. Please check the <a href="consolePlugin.html">console plugin-in guide</a> for more details. @@ -1490,7 +1490,7 @@ ALTER TABLE logging_event ADD arg3 VARCHAR(254);</pre> <p>Version 0.7.1 of logback has been released. </p> - <p>This version contains more detailled information about logback + <p>This version contains more detailed information about logback access module, and its JMX components. A <a href="access.html">dedicated page</a> explains how to configure and use logback access in Tomcat and Jetty, and access some of its @@ -1544,7 +1544,7 @@ ALTER TABLE logging_event ADD arg3 VARCHAR(254);</pre> configuration examples has been added. </p> - <p>Logback now uses continous integration in its development. + <p>Logback now uses continuous integration in its development. </p> <p>Tests have been improved, many new have been added. This release @@ -1563,7 +1563,7 @@ ALTER TABLE logging_event ADD arg3 VARCHAR(254);</pre> </p> <p>As in the previous release, a major area of work is the - documentation which is being continously improved. + documentation which is being continuously improved. </p> <hr width="80%" align="center" /> @@ -1584,7 +1584,7 @@ ALTER TABLE logging_event ADD arg3 VARCHAR(254);</pre> explaining possible reasons for the error. </p> - <p>A joran documentation was added, with examples in the core + <p>Joran documentation was added, with examples in the core module. </p> diff --git a/logback-site/src/site/pages/reasonsToSwitch.html b/logback-site/src/site/pages/reasonsToSwitch.html index 3e7592b..e8db30b 100644 --- a/logback-site/src/site/pages/reasonsToSwitch.html +++ b/logback-site/src/site/pages/reasonsToSwitch.html @@ -220,7 +220,7 @@ java.lang.Exception: 99 is invalid <p>From the above, you can recognize that the application is using Struts version 1.2.9 and was deployed under jetty version 6.1.12. Thus, stack traces will quickly inform the reader about - the classes invervening in the exception but also the package and + the classes intervening in the exception but also the package and package versions they belong to. When your customers send you a stack trace, as a developer you will no longer need to ask them to send you information about the versions of packages they are diff --git a/logback-site/src/site/pages/recipes/captureHttp.html b/logback-site/src/site/pages/recipes/captureHttp.html index 9303230..35cd684 100644 --- a/logback-site/src/site/pages/recipes/captureHttp.html +++ b/logback-site/src/site/pages/recipes/captureHttp.html @@ -66,7 +66,7 @@ <p>The <code>TeeFilter</code>, as any other servlet filter, needs to be declared in your web-application's <em>web.xml</em> - file. Here is the decleration to add to your web-application's + file. Here is the declaration to add to your web-application's <em>web.xml</em> file. </p> @@ -149,8 +149,8 @@ Set-Cookie: JSESSIONID=bgebt99ce9om;path=/logback-demo <h3><a name="disabling" href="#disabling">Disabling <code>TeeFilter</code> in the production environment</a></h3> - <p>Due to its instrusive nature, <code>TeeFilter</code> can slow - down performance. Moreover, altough we have fixed all currently + <p>Due to its intrusive nature, <code>TeeFilter</code> can slow + down performance. Moreover, although we have fixed all currently known bugs, <code>TeeFilter</code> has broken otherwise correctly behaving applications in the past. Thus, while extremely useful during problem hunting, we do not recommend @@ -178,7 +178,7 @@ Set-Cookie: JSESSIONID=bgebt99ce9om;path=/logback-demo </init-param> </filter> </pre> - <p>If it is easier to exliclitly name the integration machines, + <p>If it is easier to explicitly name the integration machines, you could list them in the includes list and omit the excludes list. </p> @@ -190,12 +190,12 @@ Set-Cookie: JSESSIONID=bgebt99ce9om;path=/logback-demo cluster. The cluster is located behind a load-balancer which probes each member of the cluster once or twice a second to check whether it is alive. Whenever a member becomes unavailable - the load-blancer will immediately (well, after at most one + the load-balancer will immediately (well, after at most one second) divert traffic from that member. </p> <p>While such a load-balancing strategy will ensure - high-availability of your web-applicaiton, it will also + high-availability of your web-application, it will also seriously pollute the access-logs with the contents of each probe made by the load-balancer. </p> @@ -218,7 +218,7 @@ X-Powered-By: Servlet 2.4; Cache-Control: no-cache Pragma: No-cache </pre> - <p>From the above, we can see that the load-blancer probes + <p>From the above, we can see that the load-balancer probes employ the <a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html#sec9.4">HTTP HEAD method</a> instead of the usual GET or POST. We can also diff --git a/logback-site/src/site/pages/recipes/emailPerTransaction.html b/logback-site/src/site/pages/recipes/emailPerTransaction.html index a7ca756..28ceead 100644 --- a/logback-site/src/site/pages/recipes/emailPerTransaction.html +++ b/logback-site/src/site/pages/recipes/emailPerTransaction.html @@ -45,10 +45,10 @@ identify the host where a particular transaction was executed</li> <li>Carol does not (or does not wish to) have access to the - hosts where Byscrit runs + hosts where Buscrit runs </li> <li>Buscrit is tested by multiple testers, e.g. Dave and Carol - and others, simultanesouly so that it is hard to identify and + and others, simultaneously so that it is hard to identify and track an individual transaction in the log files </li> </ol> @@ -159,11 +159,11 @@ public class PrimeAction extends Action { <h3>Transaction isolation</h3> <p>While the previous configuration file will trigger an outgoing - email message whenenver an event is marked with "SMTP_TRIGGER", the + email message whenever an event is marked with "SMTP_TRIGGER", the contents of the message will contain events generated by different - transactions. With a little effort, we can actually seperate events + transactions. With a little effort, we can actually separate events belonging to different transactions so that the outgoing email - triggeed at the end of the transaction contains logs from that + triggered at the end of the transaction contains logs from that transaction and only that transaction. </p> @@ -178,7 +178,7 @@ MDC.put("txId", transactionId); </pre> <p>In the <a href="http://logback-demo.qos.ch/xref/ch/qos/logback/demo/UserServletFilter.html"><code>UserServletFilter</code></a> - class, this is done by retreiving the id of the session and putting + class, this is done by retrieving the id of the session and putting it into the MDC under the key "txId".</p> @@ -248,7 +248,7 @@ MDC.put("txId", transactionId); </pre> <span class="option">to</span> options adapted for my environment) on localhost and then visiting the <a href="http://localhost:8070/logback-demo/prime.jsp">Prime - number</a> page to factoize the number 123, I received the + number</a> page to factorize the number 123, I received the following email: </p> @@ -283,7 +283,7 @@ MDC.put("txId", transactionId); </pre> </p> <p>Upon a logging event marked as SMTP_TRIGGER, the following - confugration file will trigger an email message addressed to the + configuration file will trigger an email message addressed to the value of "%mdc{txEmail}" but only if it contains the string "+log". </p> @@ -325,7 +325,7 @@ MDC.put("txId", transactionId); </pre> you can still use them within the evaluator but remove them in the recipient address with the help of the <a href="../manual/layouts.html#replace">%replace</a> conversion - word. Here is the relevant configuraton snippet:</p> + word. Here is the relevant configuration snippet:</p> <pre class="prettyprint source"><appender name="SMTP" class="ch.qos.logback.classic.net.SMTPAppender"> <to>%replace(%mdc{txEmail}){'\+log', ''}</to> @@ -352,7 +352,7 @@ MDC.put("txId", transactionId); </pre> and automatically discards buffers untouched for at least 30 minutes. While this approach will work nicely in a test environment with few transactions, in a very busy production - system, these buffer management mechanims will cause Carol to + system, these buffer management mechanisms will cause Carol to receive <a href="../manual/appenders.html#bufferManagement">truncated log buffers</a>. </p> @@ -391,7 +391,7 @@ public class PrimeAction extends Action { <p>Not that at the end of each transaction the appropriate buffer - is discarded, we can incrase the value of <span + is discarded, we can increase the value of <span class="option">maxNumberOfBuffers</span> as shown in the next configuration file.. </p> diff --git a/logback-site/src/site/pages/support.html b/logback-site/src/site/pages/support.html index 511f40e..1074acc 100644 --- a/logback-site/src/site/pages/support.html +++ b/logback-site/src/site/pages/support.html @@ -32,7 +32,7 @@ logback and <a href="http://cal10n.qos.ch/">cal10n</a> projects, we can offer you timely and competent support. Choosing our professional support service is a good way to leverage our - expertise. Moreovoer, if you require custom development we are + expertise. Moreover, if you require custom development we are likely to be of help. </p> ----------------------------------------------------------------------- Summary of changes: .../ch/qos/logback/access/pattern/NAConverter.java | 2 +- .../access/pattern/RequestURIConverter.java | 2 +- .../access/pattern/RequestURLConverter.java | 2 +- .../java/ch/qos/logback/classic/LoggerContext.java | 2 +- .../java/ch/qos/logback/classic/db/package.html | 2 +- .../logback/classic/net/SimpleSocketServer.java | 2 +- .../ch/qos/logback/classic/net/SyslogAppender.java | 2 +- .../classic/spi/LoggerContextAwareBase.java | 2 +- .../ch/qos/logback/classic/spi/LoggingEvent.java | 4 +- .../ch/qos/logback/classic/spi/LoggingEventVO.java | 2 +- .../ch/qos/logback/classic/turbo/MDCFilter.java | 2 +- .../qos/logback/classic/turbo/MatchingFilter.java | 2 +- .../classic/util/ContextSelectorStaticBinder.java | 2 +- .../logback/classic/net/mock/MockSyslogServer.java | 2 +- .../logback/core/boolex/EvaluationException.java | 2 +- .../main/java/ch/qos/logback/core/db/package.html | 2 +- .../java/ch/qos/logback/core/filter/package.html | 2 +- .../ch/qos/logback/core/helpers/Transform.java | 2 +- .../ch/qos/logback/core/net/JMSAppenderBase.java | 2 +- .../ch/qos/logback/core/net/SMTPAppenderBase.java | 4 +- .../qos/logback/core/net/SocketAppenderBase.java | 2 +- .../qos/logback/core/net/SyslogAppenderBase.java | 8 +- .../ch/qos/logback/core/pattern/FormatInfo.java | 2 +- .../logback/core/pattern/PostCompileProcessor.java | 2 +- .../ch/qos/logback/core/spi/ContextAwareBase.java | 2 +- .../ch/qos/logback/core/spi/ContextAwareImpl.java | 2 +- .../ch/qos/logback/core/rolling/FileOpener.java | 2 +- logback-site/src/site/pages/access.html | 2 +- logback-site/src/site/pages/codes.html | 4 +- logback-site/src/site/pages/consolePlugin.html | 2 +- logback-site/src/site/pages/demo.html | 6 +- logback-site/src/site/pages/documentation.html | 2 +- logback-site/src/site/pages/faq.html | 6 +- logback-site/src/site/pages/manual/appenders.html | 12 ++-- .../src/site/pages/manual/architecture.html | 2 +- .../src/site/pages/manual/configuration.html | 6 +- logback-site/src/site/pages/manual/filters.html | 20 +++--- logback-site/src/site/pages/manual/groovy.html | 2 +- .../src/site/pages/manual/introduction.html | 2 +- logback-site/src/site/pages/manual/layouts.html | 24 ++++---- logback-site/src/site/pages/manual/mdc.html | 4 +- .../src/site/pages/manual/migrationFromLog4j.html | 4 +- logback-site/src/site/pages/manual/onJoran.html | 8 +- logback-site/src/site/pages/news.html | 68 ++++++++++---------- logback-site/src/site/pages/reasonsToSwitch.html | 2 +- .../src/site/pages/recipes/captureHttp.html | 14 ++-- .../site/pages/recipes/emailPerTransaction.html | 22 +++--- logback-site/src/site/pages/support.html | 2 +- 48 files changed, 139 insertions(+), 139 deletions(-) hooks/post-receive -- Logback: the generic, reliable, fast and flexible logging framework.