- slf4j-dev - mailman3.qos.ch

[GIT] SLF4J: Simple Logging Facade for Java branch master updated. v_1.6.4-7-gc3a8646
by git-noreply＠pixie.qos.ch 01 Feb '12

01 Feb '12

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 "SLF4J: Simple Logging Facade for Java". The branch, master has been updated via c3a8646b285aee7d57bf13fecc3749ffefcbb944 (commit) from c62ff134a33eecc63ed01407387a614fdab3b7b3 (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=slf4j.git;a=commit;h=c3a8646b285aee7d57bf13fecc… http://github.com/ceki/slf4j/commit/c3a8646b285aee7d57bf13fecc3749ffefcbb944 commit c3a8646b285aee7d57bf13fecc3749ffefcbb944 Author: Ceki Gulcu <ceki(a)qos.ch> Date: Wed Feb 1 17:30:17 2012 +0100 minor editing diff --git a/slf4j-site/src/site/pages/localization.html b/slf4j-site/src/site/pages/localization.html index 94a078f..186f783 100644 --- a/slf4j-site/src/site/pages/localization.html +++ b/slf4j-site/src/site/pages/localization.html @@ -48,7 +48,7 @@ - Let assume that you have defined localized message your + Let us assume that you have defined localized message in your application. In accordance with the CAL10N's philopshopy, you have the declared the keys for those messages in the enum type <code>Production</code>. ----------------------------------------------------------------------- Summary of changes: slf4j-site/src/site/pages/localization.html | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) hooks/post-receive -- SLF4J: Simple Logging Facade for Java

1 0

[GIT] SLF4J: Simple Logging Facade for Java branch master updated. v_1.6.4-6-gc62ff13
by git-noreply＠pixie.qos.ch 01 Jan '12

01 Jan '12

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 "SLF4J: Simple Logging Facade for Java". The branch, master has been updated via c62ff134a33eecc63ed01407387a614fdab3b7b3 (commit) from c40b8ac3eaae7730c3e4cd07e2550415f7881a2f (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=slf4j.git;a=commit;h=c62ff134a33eecc63ed0140738… http://github.com/ceki/slf4j/commit/c62ff134a33eecc63ed01407387a614fdab3b7b3 commit c62ff134a33eecc63ed01407387a614fdab3b7b3 Author: Ceki Gulcu <ceki(a)qos.ch> Date: Sun Jan 1 13:17:05 2012 +0100 2012 copyright, cosmetic changes diff --git a/slf4j-site/src/site/pages/codes.html b/slf4j-site/src/site/pages/codes.html index d38a408..ba5bd00 100644 --- a/slf4j-site/src/site/pages/codes.html +++ b/slf4j-site/src/site/pages/codes.html @@ -103,7 +103,7 @@ problem. - As of SLF4J version 1.6, in the absence of a binding, SLF4J + since 1.6.0 As of SLF4J version 1.6, in the absence of a binding, SLF4J will default to a no-operation (NOP) logger implementation. @@ -160,9 +160,9 @@ to use the nop (no-operation) binding, then remove slf4j-simple-${version}.jar from the class path. - Note that the warning emitted by SLF4J is just that, a - warning. SLF4J will still bind with the first framework it finds - on the class path. + Note The warning emitted by + SLF4J is just that, a warning. SLF4J will still bind with the + first framework it finds on the class path.  @@ -181,11 +181,11 @@ slf4j-simple-${project.version}.jar, using slf4j-simple-1.5.5.jar will not work. - It should be noted that from the client's perspective all - versions of slf4j-api are compatible. Client code compiled with - slf4j-api-N.jar will run perfectly fine with - slf4j-api-M.jar for any N and M. You only need to ensure - that the version of your binding matches that of the + Note From the client's + perspective all versions of slf4j-api are compatible. Client code + compiled with slf4j-api-N.jar will run perfectly fine + with slf4j-api-M.jar for any N and M. You only need to + ensure that the version of your binding matches that of the slf4j-api.jar. You do not have to worry about the version of slf4j-api.jar used by a given dependendency in your project. You can always use any version of slf4j-api.jar, and as long @@ -250,10 +250,10 @@ at org.apache.log4j.LogManager.getLogger(LogManager.java:39) subsequent lines omitted...</pre> - As of SLF4J version 1.5.11, the code preempts the inevitable - stack overflow error by throwing an exception with details about - the actual cause of the problem. This is deemed to be better than - leaving the user wondering about the reasons of the + Since 1.5.11 SLF4J software preempts + the inevitable stack overflow error by throwing an exception with + details about the actual cause of the problem. This is deemed to + be better than leaving the user wondering about the reasons of the <code>StackOverflowError</code>. @@ -295,10 +295,10 @@ subsequent lines omitted...</pre> - As of SLF4J version 1.5.11, the code preempts the inevitable - stack overflow error by throwing an exception with details about - the actual cause of the problem. This is deemed to be better than - leaving the user wondering about the reasons of the + Since 1.5.11 SLF4J software preempts + the inevitable stack overflow error by throwing an exception with + details about the actual cause of the problem. This is deemed to + be better than leaving the user wondering about the reasons of the <code>StackOverflowError</code>. diff --git a/slf4j-site/src/site/pages/css/site.css b/slf4j-site/src/site/pages/css/site.css index c37215c..def6249 100644 --- a/slf4j-site/src/site/pages/css/site.css +++ b/slf4j-site/src/site/pages/css/site.css @@ -139,10 +139,13 @@ strong { } .menuGroup { - border: 1px solid #cccccc; - background-color: #ffffff; + border: 1px solid #cccccc; + background-color: #fff8e8; color: #564b47; border: 1px solid #cccccc; + -webkit-border-radius: 3px; + -moz-border-radius: 3px; + border-radius: 3px; } .menuGroup a { @@ -150,7 +153,7 @@ strong { width: 95.5%; margin: 0px; padding: 2px; - border: solid 1px #FFFFFF; + border: solid 1px #fff8e8; color: #0066cc; text-decoration: none; } @@ -159,6 +162,9 @@ strong { border: solid 1px #FFFFFF; background-color: #3333CC; color: #ffffff; + -webkit-border-radius: 3px; + -moz-border-radius: 3px; + border-radius: 3px; } .pub { @@ -330,4 +336,6 @@ table.bodyTable tr.alt { -moz-border-radius: 3px; border-radius: 3px; } - +.label.notice { + background-color: #62cffc; +} diff --git a/slf4j-site/src/site/pages/manual.html b/slf4j-site/src/site/pages/manual.html index 4bd52d1..4b70707 100644 --- a/slf4j-site/src/site/pages/manual.html +++ b/slf4j-site/src/site/pages/manual.html @@ -29,7 +29,7 @@ the addition of only a single mandatory dependency, namely slf4j-api-${project.version}.jar. - New If no binding is found on the + since 1.6.0 If no binding is found on the class path, then SLF4J will default to a no-operation implementation. diff --git a/slf4j-site/src/site/pages/templates/footer.js b/slf4j-site/src/site/pages/templates/footer.js index 3b2a18a..4d75cfd 100644 --- a/slf4j-site/src/site/pages/templates/footer.js +++ b/slf4j-site/src/site/pages/templates/footer.js @@ -10,7 +10,7 @@ document.write(' <td>') //document.write(' alt="Valid XHTML 1.0 Transitional" height="31" width="88" /></a>') document.write(' </td>') -document.write('<td valign="top">Copyright © 2004-2011 <a href="http://www.qos.ch/">QOS.ch</a></td>') +document.write('<td valign="top">Copyright © 2004-2012 <a href="http://www.qos.ch/">QOS.ch</a></td>') document.write('</tr>') document.write('</table>') ----------------------------------------------------------------------- Summary of changes: slf4j-site/src/site/pages/codes.html | 34 ++++++++++++------------ slf4j-site/src/site/pages/css/site.css | 16 +++++++++--- slf4j-site/src/site/pages/manual.html | 2 +- slf4j-site/src/site/pages/templates/footer.js | 2 +- 4 files changed, 31 insertions(+), 23 deletions(-) hooks/post-receive -- SLF4J: Simple Logging Facade for Java

1 0

[GIT] SLF4J: Simple Logging Facade for Java branch master updated. v_1.6.4-5-gc40b8ac
by git-noreply＠pixie.qos.ch 30 Dec '11

30 Dec '11

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 "SLF4J: Simple Logging Facade for Java". The branch, master has been updated via c40b8ac3eaae7730c3e4cd07e2550415f7881a2f (commit) from fa9d46dca9b8d476d137d276315fa557d818992b (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=slf4j.git;a=commit;h=c40b8ac3eaae7730c3e4cd07e2… http://github.com/ceki/slf4j/commit/c40b8ac3eaae7730c3e4cd07e2550415f7881a2f commit c40b8ac3eaae7730c3e4cd07e2550415f7881a2f Author: Ceki Gulcu <ceki(a)qos.ch> Date: Fri Dec 30 19:08:14 2011 +0100 edits, css changes diff --git a/slf4j-site/src/site/pages/css/site.css b/slf4j-site/src/site/pages/css/site.css index f134534..c37215c 100644 --- a/slf4j-site/src/site/pages/css/site.css +++ b/slf4j-site/src/site/pages/css/site.css @@ -42,7 +42,7 @@ a { .source { border-top: 1px solid #DDDDDD; border-bottom: 1px solid #DDDDDD; - background:#eee; + background:#f5f5f5; font-family: Courier, "MS Courier New", Prestige, Everson Monocourrier, monospace; padding-bottom: 0.5ex; padding-top: 0.5ex; @@ -52,11 +52,15 @@ a { margin-top: 0.5ex; margin-bottom: 0.5ex; white-space: pre; + + -webkit-border-radius: 3px; + -moz-border-radius: 3px; + border-radius: 3px; } pre { background-color:transparent; - font-family: Courier, Monaco, Monospace; + font-family: Monaco, Andale Mono, Courier New, monospace; } .alignright { @@ -305,5 +309,25 @@ table.bodyTable tr.alt { background-color: #eee; } +.striped tr:nth-child(odd) td { + background-color: #f9f9f9; +} +.striped td { + background-color: #f0f0f0; +} + /* EOF =============== bodyTable =============== */ +.label { + padding: 1px 3px 2px; + font-size: 9.75px; + font-weight: bold; + color: #ffffff; + text-transform: uppercase; + white-space: nowrap; + background-color: #bfbfbf; + -webkit-border-radius: 3px; + -moz-border-radius: 3px; + border-radius: 3px; +} + diff --git a/slf4j-site/src/site/pages/manual.html b/slf4j-site/src/site/pages/manual.html index c26b47c..4bd52d1 100644 --- a/slf4j-site/src/site/pages/manual.html +++ b/slf4j-site/src/site/pages/manual.html @@ -22,13 +22,15 @@ <h2>SLF4J user manual</h2> The Simple Logging Facade for Java or (SLF4J) serves as a - simple facade or abstraction for various logging frameworks, e.g. - java.util.logging, log4j and logback, allowing the end-user to - plug in the desired logging framework at deployment time. - Note that SLF4J-enabling your library/application implies the - addition of only a single mandatory dependency, namely - slf4j-api-${project.version}.jar. If no binding is found - on the class path, then SLF4J will default to a no-operation + simple facade or abstraction for various logging frameworks, such + as java.util.logging, log4j and logback. SLF4J allows the end-user + to plug in the desired logging framework at deployment + time. Note that SLF4J-enabling your library/application implies + the addition of only a single mandatory dependency, namely + slf4j-api-${project.version}.jar. + + New If no binding is found on the + class path, then SLF4J will default to a no-operation implementation. @@ -193,14 +195,10 @@ SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further detail the general idea. -   - <a href="images/concrete-bindings.png"> - <img border="1" src="images/concrete-bindings.png" alt="click to enlarge" width="500"/> + <img border="1" src="images/concrete-bindings.png" alt="click to enlarge" width="800"/> </a> -   - The SLF4J interfaces and their various adapters are extremely simple. Most developers familiar with the Java language should be able to read and fully understand the code in less than one @@ -294,13 +292,13 @@ SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further detail summary</a> </h3> - <table class="bodyTable" cellspacing="4" cellpadding="4"> + <table class="bodyTable striped" cellspacing="4" cellpadding="4"> <tr> <th align="left">Advantage</th> <th align="left">Description</th> </tr> - <tr class="a"> + <tr> <td>Select your logging framework at deployment time</td> @@ -311,7 +309,7 @@ SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further detail </tr> - <tr class="alt"> + <tr> <td>Fail-fast operation</td> <td>Due to the way that classes are loaded by the JVM, the @@ -322,7 +320,7 @@ SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further detail </tr> - <tr class="a"> + <tr> <td>Bindings for popular logging frameworks </td> @@ -333,7 +331,7 @@ SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further detail </tr> - <tr class="alt"> + <tr> <td>Bridging legacy logging APIs</td> <td> @@ -350,7 +348,7 @@ SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further detail </td> </tr> - <tr class="a"> + <tr> <td>Migrate your source code</td> <td>The <a href="migrator.html">slf4j-migrator</a> utility can help you migrate your source to use SLF4J. @@ -359,7 +357,7 @@ SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further detail - <tr class="alt"> + <tr> <td>Support for parameterized log messages</td> <td>All SLF4J bindings support parameterized log messages diff --git a/slf4j-site/src/site/resources/images/concrete-bindings.png b/slf4j-site/src/site/resources/images/concrete-bindings.png index 118216c..8af5e5b 100644 Binary files a/slf4j-site/src/site/resources/images/concrete-bindings.png and b/slf4j-site/src/site/resources/images/concrete-bindings.png differ diff --git a/slf4j-site/src/site/resources/images/core-bindings.png b/slf4j-site/src/site/resources/images/core-bindings.png deleted file mode 100644 index 0fbb26a..0000000 Binary files a/slf4j-site/src/site/resources/images/core-bindings.png and /dev/null differ diff --git a/slf4j-site/src/site/resources/images/core-bindings1.png b/slf4j-site/src/site/resources/images/core-bindings1.png deleted file mode 100644 index 0fbb26a..0000000 Binary files a/slf4j-site/src/site/resources/images/core-bindings1.png and /dev/null differ diff --git a/slf4j-site/src/site/resources/images/core-bindings2.png b/slf4j-site/src/site/resources/images/core-bindings2.png deleted file mode 100644 index 0fbb26a..0000000 Binary files a/slf4j-site/src/site/resources/images/core-bindings2.png and /dev/null differ diff --git a/slf4j-site/src/site/resources/images/core-bindings3.png b/slf4j-site/src/site/resources/images/core-bindings3.png deleted file mode 100644 index 0fbb26a..0000000 Binary files a/slf4j-site/src/site/resources/images/core-bindings3.png and /dev/null differ ----------------------------------------------------------------------- Summary of changes: slf4j-site/src/site/pages/css/site.css | 28 ++++++++++++++- slf4j-site/src/site/pages/manual.html | 36 +++++++++---------- .../site/resources/images/concrete-bindings.png | Bin 125870 -> 77852 bytes .../src/site/resources/images/core-bindings.png | Bin 16006 -> 0 bytes .../src/site/resources/images/core-bindings1.png | Bin 16006 -> 0 bytes .../src/site/resources/images/core-bindings2.png | Bin 16006 -> 0 bytes .../src/site/resources/images/core-bindings3.png | Bin 16006 -> 0 bytes 7 files changed, 43 insertions(+), 21 deletions(-) delete mode 100644 slf4j-site/src/site/resources/images/core-bindings.png delete mode 100644 slf4j-site/src/site/resources/images/core-bindings1.png delete mode 100644 slf4j-site/src/site/resources/images/core-bindings2.png delete mode 100644 slf4j-site/src/site/resources/images/core-bindings3.png hooks/post-receive -- SLF4J: Simple Logging Facade for Java

1 0

[GIT] SLF4J: Simple Logging Facade for Java branch master updated. v_1.6.4-4-gfa9d46d
by git-noreply＠pixie.qos.ch 23 Dec '11

23 Dec '11

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 "SLF4J: Simple Logging Facade for Java". The branch, master has been updated via fa9d46dca9b8d476d137d276315fa557d818992b (commit) from bc2121efb6437fe4b2deef38be9a0588c94627ba (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=slf4j.git;a=commit;h=fa9d46dca9b8d476d137d27631… http://github.com/ceki/slf4j/commit/fa9d46dca9b8d476d137d276315fa557d818992b commit fa9d46dca9b8d476d137d276315fa557d818992b Author: Ceki Gulcu <ceki(a)qos.ch> Date: Fri Dec 23 19:06:02 2011 +0100 typo fix diff --git a/slf4j-site/src/site/pages/faq.html b/slf4j-site/src/site/pages/faq.html index c17de0c..c1d5fb8 100644 --- a/slf4j-site/src/site/pages/faq.html +++ b/slf4j-site/src/site/pages/faq.html @@ -720,7 +720,7 @@ org.slf4j.impl.StaticLoggerBinder.SINGLETON from class org.slf4j.LoggerFactory An alternative approach is to depend on an empty commons-logging.jar artifact. This clever <a href="http://day-to-day-stuff.blogspot.com/2007/10/announcement-version-99-does-n…">approach - first was imagined</a> imagined and initially supported by Erik van + first was imagined</a> and initially supported by Erik van Oosten. ----------------------------------------------------------------------- Summary of changes: slf4j-site/src/site/pages/faq.html | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) hooks/post-receive -- SLF4J: Simple Logging Facade for Java

1 0

[GIT] SLF4J: Simple Logging Facade for Java branch master updated. v_1.6.4-3-gbc2121e
by git-noreply＠pixie.qos.ch 02 Dec '11

02 Dec '11

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 "SLF4J: Simple Logging Facade for Java". The branch, master has been updated via bc2121efb6437fe4b2deef38be9a0588c94627ba (commit) from 3a461317916651390d83891d3d4b73d9e38dcb28 (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=slf4j.git;a=commit;h=bc2121efb6437fe4b2deef38be… http://github.com/ceki/slf4j/commit/bc2121efb6437fe4b2deef38be9a0588c94627ba commit bc2121efb6437fe4b2deef38be9a0588c94627ba Author: Ceki Gulcu <ceki(a)qos.ch> Date: Sat Dec 3 00:08:21 2011 +0100 editorial changes diff --git a/slf4j-site/src/site/pages/faq.html b/slf4j-site/src/site/pages/faq.html index afec6fd..c17de0c 100644 --- a/slf4j-site/src/site/pages/faq.html +++ b/slf4j-site/src/site/pages/faq.html @@ -666,11 +666,15 @@ org.slf4j.impl.StaticLoggerBinder.SINGLETON from class org.slf4j.LoggerFactory alternative 1) explicit exlusion Many software projects using Maven declare commons-logging as - a dependency. Thus, if you wish to migrate to SLF4J or use + a dependency. Therefore, if you wish to migrate to SLF4J or use jcl-over-slf4j, you would need to exclude commons-logging in all of your project's dependencies which transitively depend on - commons-logging. Excluding commons-logging explicitly can be a - cumbersome and an error prone process. + commons-logging. <a + href="http://maven.apache.org/guides/introduction/introduction-to-optional-and-ex…">Dependency + exclusion</a> is described in the Maven documentation. Excluding + commons-logging explicitly for multiple dependencies distributed + on several pom.xml files can be a cumbersome and a + relatively error prone process. alternative 2) provided scope @@ -713,19 +717,23 @@ org.slf4j.impl.StaticLoggerBinder.SINGLETON from class org.slf4j.LoggerFactory alternative 3) empty artifacts - An alternative approach is to depend on an empty + An alternative approach is to depend on an empty commons-logging.jar artifact. This clever <a href="http://day-to-day-stuff.blogspot.com/2007/10/announcement-version-99-does-n…">approach - was imagined</a> imagined and initially supported by Erik van + first was imagined</a> imagined and initially supported by Erik van Oosten. The empty artifact is available from a <a href="http://version99.qos.ch">http://version99.qos.ch</a> a - highly available Maven repository, replicated by several hosts - located in different geographical regions. The following - decleration adds the version99 repository to the set of remote - repositories searched by Maven. + high-availability Maven repository, replicated on several hosts + located in different geographical regions. + + The following decleration adds the version99 repository to + the set of remote repositories searched by Maven. This + repository contains empty artifacts for commons-logging and + log4j. By the way, if you use the version99 repository, please + drop us a line at <version99 AT qos.ch>. <pre class="prettyprint source"><repositories> @@ -736,30 +744,38 @@ org.slf4j.impl.StaticLoggerBinder.SINGLETON from class org.slf4j.LoggerFactory </repository> </repositories></pre> - Once you declare version 99-empty of commons-logging in the - <code><dependencyManagement></code> section of your project, - all transtive dependencies for commons-logging will also use - version 99-empty, thus nicely addressing the commons-logging - exclusion problem. + Declaring version 99-empty of commons-logging in the + <code><dependencyManagement></code> section of your project + will direct all transtive dependencies for commons-logging to + import version 99-empty, thus nicely addressing the + commons-logging exclusion problem. The classes for commons-logging + will be provided by jcl-over-slf4j. The following lines declare + commons-logging version 99-empty (in the dependency management + section) and declare jcl-over-slf4j as a dependency. <pre class="prettyprint source"><dependencyManagement> - <dependency> - <groupId>commons-logging</groupId> - <artifactId>commons-logging</artifactId> - <version>99-empty</version> - </dependency> - ... other declarations... + <dependencies> + <dependency> + <groupId>commons-logging</groupId> + <artifactId>commons-logging</artifactId> + <version>99-empty</version> + </dependency> + ... other declarations... + </dependencies> </dependencyManagement> - + + + <dependencies> <dependency> <groupId>org.slf4j</groupId> <artifactId>jcl-over-slf4j</artifactId> <version>${project.version}</version> </dependency> -<dependencies> + ... other dependency declarations +</dependencies> </pre> ----------------------------------------------------------------------- Summary of changes: slf4j-site/src/site/pages/faq.html | 60 ++++++++++++++++++++++------------- 1 files changed, 38 insertions(+), 22 deletions(-) hooks/post-receive -- SLF4J: Simple Logging Facade for Java

1 0

org.slf4j.NDC implementation problem
by Antony Bowesman 23 Nov '11

23 Nov '11

I'm migrating a log4j environment to SLF4J. Our log4j usage makes use of NDC as a small stack and I'm using the ext package to use the slf4j NDC. However, the problem is that the NDC implementation just sits on top of MDC and the MDC context is inherited by threads, whereas NDC is NOT, unless inherit() is called specifically. I then went to patch my NDC usage to call NDC.clear(), but the org.slf4j.NDC does not expose it. This means the log output contains the NDC context from my root thread and there's no way to clear any of the context. So, I have patched NDC as attached. Is there any reason why this cannot be taken to the core code? Antony

2 2

[GIT] SLF4J: Simple Logging Facade for Java branch master updated. v_1.6.4-2-g3a46131
by git-noreply＠pixie.qos.ch 12 Nov '11

12 Nov '11

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 "SLF4J: Simple Logging Facade for Java". The branch, master has been updated via 3a461317916651390d83891d3d4b73d9e38dcb28 (commit) from ccd1c8355b9ed6c77b375d7efd459416f10fb62e (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=slf4j.git;a=commit;h=3a461317916651390d83891d3d… http://github.com/ceki/slf4j/commit/3a461317916651390d83891d3d4b73d9e38dcb28 commit 3a461317916651390d83891d3d4b73d9e38dcb28 Author: Ceki Gulcu <ceki(a)qos.ch> Date: Sat Nov 12 16:12:16 2011 +0100 docs on version 99 diff --git a/slf4j-site/src/site/pages/faq.html b/slf4j-site/src/site/pages/faq.html index b226ac4..afec6fd 100644 --- a/slf4j-site/src/site/pages/faq.html +++ b/slf4j-site/src/site/pages/faq.html @@ -78,7 +78,7 @@ </li> <li> - <a href="#maven2">What about Maven 2 transitive + <a href="#maven2">What about Maven transitive dependencies? </a> </li> @@ -609,18 +609,19 @@ org.slf4j.impl.StaticLoggerBinder.SINGLETON from class org.slf4j.LoggerFactory  - <dt><a name="maven2" href="#maven2">What about Maven2 + <dt><a name="maven2" href="#maven2">What about Maven transitive dependencies? </a> </dt> <dd> - As an author of a library built with Maven2, you might - want to test your application using a binding, say - slf4j-log4j12 or logback-classic, without forcing log4j or - logback-classic as a dependency upon your users. As of SLF4J - version 1.3, this quite easy to accomplish. But first, since - your library's code depends on the SLF4J API you will need to - declare slf4j-api as a compile-time (default scope) + As an author of a library built with Maven, you might want to + test your application using a binding, say slf4j-log4j12 or + logback-classic, without forcing log4j or logback-classic as a + dependency upon your users. This is rather easy to accomplish. + + + Given that your library's code depends on the SLF4J API, you + will need to declare slf4j-api as a compile-time (default scope) dependency. <pre class="prettyprint source"><dependency> @@ -662,18 +663,20 @@ org.slf4j.impl.StaticLoggerBinder.SINGLETON from class org.slf4j.LoggerFactory </dt> <dd> + alternative 1) explicit exlusion + Many software projects using Maven declare commons-logging as a dependency. Thus, if you wish to migrate to SLF4J or use - jcl-over-slf4j, you would need to declare a commons-logging - exclusion in all of your dependencies which transitively depend - on commons-logging. This can be an error prone process. To - alleviate the pain, Erik van Oosten has developed a <a - href="http://day-to-day-stuff.blogspot.com/2007/10/announcement-version-99-does-n…">clever - hack around this problem.</a> + jcl-over-slf4j, you would need to exclude commons-logging in all + of your project's dependencies which transitively depend on + commons-logging. Excluding commons-logging explicitly can be a + cumbersome and an error prone process. - Alternatively, commons-logging can be rather simply and - conveniently excluded as a dependency by declaring it in the + alternative 2) provided scope + + Commons-logging can be rather simply and conveniently + excluded as a dependency by declaring it in the provided scope within the pom.xml file of your project. The actual commons-logging classes would be provided by jcl-over-slf4j. This translates into the following pom file @@ -700,6 +703,66 @@ org.slf4j.impl.StaticLoggerBinder.SINGLETON from class org.slf4j.LoggerFactory true. + Unfortunately, while declaring commons-logging in the + provided scope gets the job done, your IDE, e.g. Eclipse, will + still place commons-logging.jar on your projet's class + path as seen by your IDE. You would need to make sure that + jcl-over-slf4j.jar is visible before + commons-logging.jar by your IDE. + + + alternative 3) empty artifacts + + An alternative approach is to depend on an empty + commons-logging.jar artifact. This clever <a + href="http://day-to-day-stuff.blogspot.com/2007/10/announcement-version-99-does-n…">approach + was imagined</a> imagined and initially supported by Erik van + Oosten. + + + The empty artifact is available from a <a + href="http://version99.qos.ch">http://version99.qos.ch</a> a + highly available Maven repository, replicated by several hosts + located in different geographical regions. The following + decleration adds the version99 repository to the set of remote + repositories searched by Maven. + + + <pre class="prettyprint source"><repositories> + <repository> + <id>version99</id> +  + <url>http://version99.qos.ch/</url> + </repository> +</repositories></pre> + + Once you declare version 99-empty of commons-logging in the + <code><dependencyManagement></code> section of your project, + all transtive dependencies for commons-logging will also use + version 99-empty, thus nicely addressing the commons-logging + exclusion problem. + + +<pre class="prettyprint source"><dependencyManagement> + <dependency> + <groupId>commons-logging</groupId> + <artifactId>commons-logging</artifactId> + <version>99-empty</version> + </dependency> + ... other declarations... +</dependencyManagement> + + +<dependencies> + <dependency> + <groupId>org.slf4j</groupId> + <artifactId>jcl-over-slf4j</artifactId> + <version>${project.version}</version> + </dependency> +<dependencies> +</pre> + + </dd> ----------------------------------------------------------------------- Summary of changes: slf4j-site/src/site/pages/faq.html | 97 +++++++++++++++++++++++++++++------ 1 files changed, 80 insertions(+), 17 deletions(-) hooks/post-receive -- SLF4J: Simple Logging Facade for Java

1 0

version 99
by ceki 12 Nov '11

12 Nov '11

Hello all, Building on Erik van Oosten's version99-does-not exist, I've created a highly-available repository serving empty commons-logging and log4j artifacts. Here are the docs, http://www.slf4j.org/faq.html#excludingJCL Your comments are welcome, -- Ceki http://twitter.com/#!/ceki

1 0

[GIT] SLF4J: Simple Logging Facade for Java branch master updated. v_1.6.4-1-gccd1c83
by git-noreply＠pixie.qos.ch 07 Nov '11

07 Nov '11

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 "SLF4J: Simple Logging Facade for Java". The branch, master has been updated via ccd1c8355b9ed6c77b375d7efd459416f10fb62e (commit) from 38915dafe04496b42ec65732c9376aa26b3c81e9 (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=slf4j.git;a=commit;h=ccd1c8355b9ed6c77b375d7efd… http://github.com/ceki/slf4j/commit/ccd1c8355b9ed6c77b375d7efd459416f10fb62e commit ccd1c8355b9ed6c77b375d7efd459416f10fb62e Author: Ceki Gulcu <ceki(a)qos.ch> Date: Mon Nov 7 19:40:22 2011 +0100 improved javadocs diff --git a/slf4j-api/src/main/java/org/slf4j/spi/LocationAwareLogger.java b/slf4j-api/src/main/java/org/slf4j/spi/LocationAwareLogger.java index b440a56..5177f24 100644 --- a/slf4j-api/src/main/java/org/slf4j/spi/LocationAwareLogger.java +++ b/slf4j-api/src/main/java/org/slf4j/spi/LocationAwareLogger.java @@ -30,10 +30,10 @@ import org.slf4j.Marker; /** * An optional interface helping integration with logging systems capable of * extracting location information. This interface is mainly used by SLF4J bridges - * such as jcl104-over-slf4j which need to provide hints so that the underlying logging - * system can extract the correct location information (method name, line number, etc.). - * - * + * such as jcl-over-slf4j, jul-to-slf4j and log4j-over-slf4j or {@link Logger} wrappers + * which need to provide hints so that the underlying logging system can extract + * the correct location information (method name, line number). + * * @author Ceki Gulcu * @since 1.3 */ @@ -49,11 +49,12 @@ public interface LocationAwareLogger extends Logger { /** * Printing method with support for location information. * - * @param marker - * @param fqcn The fully qualified class name of the caller - * @param level - * @param message - * @param t + * @param marker The marker to be used for this event, may be null. + * @param fqcn The fully qualified class name of the logger instance, + * typically the logger class, logger bridge or a logger wrapper. + * @param level One of the level integers defined in this interface + * @param message The message for the log event + * @param t Throwable associated with the log event, may be null. */ public void log(Marker marker, String fqcn, int level, String message, Object[] argArray, Throwable t); ----------------------------------------------------------------------- Summary of changes: .../java/org/slf4j/spi/LocationAwareLogger.java | 19 ++++++++++--------- 1 files changed, 10 insertions(+), 9 deletions(-) hooks/post-receive -- SLF4J: Simple Logging Facade for Java

1 0

Release of SLF4J version 1.6.4
by ceki 31 Oct '11

31 Oct '11

Hello all, I am happy to announce the immediate availability of SLF4J version 1.6.4 consisting bug fixes and documentation improvements. It should hit the Maven central repository within the next 24 hours. The Simple Logging Facade for Java or (SLF4J) serves as a simple facade or abstraction for various logging frameworks, e.g. java.util.logging, log4j and logback, allowing the end user to plug in the desired logging framework at deployment time. In the 1.6.x series, in the absence of an SLF4J binding, slf4j-api will default to a no-operation implementation discarding all log requests. Thus, instead of throwing an exception, SLF4J will emit a single warning message about the absence of a binding and proceed to discard all log requests without further protest. In other words, libraries no longer need to bundle an slf4j binding along with slf4j-api.jar in order to function out-of-the-box. Please refer to the the news page for precise details. http://www.slf4j.org/news.html You can download SLF4J, including full source code, class files and documentation on our download page, shown below. http://www.slf4j.org/download.html You can receive SLF4J related announcements by subscribing to the SLF4J announce mailing list. To subscribe to QOS.ch announce list, please visit the following URL. http://www.qos.ch/mailman/listinfo/announce -- Ceki http://twitter.com/#!/ceki

1 0