- slf4j-dev - mailman3.qos.ch

[Bug 192] New: Update Logger javadocs to reflect changes due to fixing bug 70
by bugzilla-daemon＠pixie.qos.ch 16 Jul '10

16 Jul '10

http://bugzilla.slf4j.org/show_bug.cgi?id=192 Summary: Update Logger javadocs to reflect changes due to fixing bug 70 Product: SLF4J Version: 1.6.x Platform: PC URL: http://www.qos.ch/pipermail/slf4j-user/2010- July/000969.html OS/Version: Windows NT Status: NEW Severity: major Priority: P1 Component: Core API AssignedTo: slf4j-dev(a)qos.ch ReportedBy: listid(a)qos.ch Hi, I see that this change was made in 1.6.x: "In the presence of multiple parameters and if the last argument in a logging statement is an exception, then SLF4J will now presume that the user wants the last argument to be treated as an exception and not a simple parameter. See the relevant FAQ entry for further details. This fixes bug 70 submitted by Joern Huxhorn who also provided the relevant patch." Can someone update the javadocs for the relevant Logger methods to reflect this new behavior? Thanks, Ari -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 0

[GIT] SLF4J: Simple Logging Facade for Java branch, master, updated. v_1.6.1-1-g14b4011
by git-noreply＠pixie.qos.ch 14 Jul '10

14 Jul '10

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 14b4011e47ee2c6452af2cf066b5d930d4da11b3 (commit) from 990f24180a7fe18040a851a71f6fab06a4f18604 (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=14b4011e47ee2c6452af2cf066… http://github.com/ceki/slf4j/commit/14b4011e47ee2c6452af2cf066b5d930d4da11b3 commit 14b4011e47ee2c6452af2cf066b5d930d4da11b3 Author: Ceki Gulcu <ceki(a)qos.ch> Date: Wed Jul 14 17:01:14 2010 +0200 doc edits diff --git a/slf4j-site/src/site/pages/codes.html b/slf4j-site/src/site/pages/codes.html index ff2281c..bcbd015 100644 --- a/slf4j-site/src/site/pages/codes.html +++ b/slf4j-site/src/site/pages/codes.html @@ -320,21 +320,20 @@ version does not match that of the binding</a></h3> <p>Mixing mixing different versions of slf4j artifacts can cause - problems. For example, if you are using slf4j-api-1.5.5.jar, then - you should also use slf4j-simple-1.5.5.jar, using - slf4j-simple-1.4.2.jar will not work. + problems. For example, if you are using + slf4j-api-${project.version}.jar, then you should also use + slf4j-simple-${project.version}.jar, using slf4j-simple-1.5.5.jar + will not work. </p> - <p>In general, you should make sure that the slf4j-api version - matches that of the slf4j binding. + <p class="red">In general, you should make sure that the + slf4j-api version matches that of the slf4j binding. </p> <p>At initialization time, if SLF4J suspects that there may be a - mismatch problem, it emits a warning about the said mismatch. - </p> - - <p>For the exact details of the version mismatch detection - mechanism, please refer to the <a + version mismatch problem, it will emit a warning about the + suspected mismatch. For the exact details of the version mismatch + detection mechanism, please refer to the <a href="faq.html#version_checks">relevant entry</a> in the FAQ. </p> diff --git a/slf4j-site/src/site/pages/faq.html b/slf4j-site/src/site/pages/faq.html index 2b26572..d079147 100644 --- a/slf4j-site/src/site/pages/faq.html +++ b/slf4j-site/src/site/pages/faq.html @@ -1245,9 +1245,9 @@ try { <dd> <p>The version check performed by SLF4J API during its - initialization is an elective process. Conforming SLF4J - implementations may choose <em>not</em> to participate, in - which case, no version check will be performed. + initialization is an <em>elective</em> process. Conforming SLF4J + implementations may choose <em>not</em> to participate, in which + case, no version check will be performed. </p> <p>However, if an SLF4J implementation decides to participate, @@ -1273,23 +1273,17 @@ try { <p><b>As of SLF4J 1.5.5</b>, all bindings shipped within the SLF4J distribution, e.g. slf4j-logj12, slf4j-simple and slf4j-jdk14, declare the REQUESTED_API_VERSION field with a - value equal to their SLF4J version. It follows that, for - example if slf4j-simple-1.5.6.jar is mixed with - slf4j-api-1.5.5.jar, then a version mismatch warning will be - issued. Note that SLF4J versions prior to 1.5.5 did not have a - version check mechanism. Only slf4j-api-1.5.5.jar and later - can emit version mismatch warnings. (Actually, version 1.5.4 - offered a check policy which was much too restrictive and - inconsistent with the size of our user base. Consequently, - SLF4J version 1.5.5 was released just a day after 1.5.4.) - </p> - - <p>Given its large installed user base and several external - implementations, it would have been unwise to expect all SLF4J - implementations to closely follow SLF4J's release schedule, let - alone align their release schedules with SLF4J. Hence, the - elective version check policy. + value equal to their SLF4J version. It follows that, for example + if slf4j-simple-1.5.8.jar is mixed with slf4j-api-1.6.0.jar, + given that 1.5.8 is not on the compatibility list of SLF4J + version 1.6.x, a version mismatch warning will be issued. </p> + + <p>Note that SLF4J versions prior to 1.5.5 did not have a + version check mechanism. Only slf4j-api-1.5.5.jar and later can + emit version mismatch warnings. + </p> + </dd> diff --git a/slf4j-site/src/site/pages/manual.html b/slf4j-site/src/site/pages/manual.html index 0f51f00..0c79c40 100644 --- a/slf4j-site/src/site/pages/manual.html +++ b/slf4j-site/src/site/pages/manual.html @@ -191,9 +191,9 @@ public class HelloWorld { (JCL). </p> - <p>Hopefully, the simplicity of the SLF4J interfaces and the - deployment model will make it easy for developers of other - logging frameworks to conform to the SLF4J model. + <p>Given the simplicity of the SLF4J interfaces and its + deployment model, developers of new logging frameworks should + find it very easy to write SLF4J bindings. </p> <h3><a name="libraries" href="#libraries">Libraries</a></h3> @@ -201,17 +201,20 @@ public class HelloWorld { <p>Authors of widely-distributed components and libraries may code against the SLF4J interface in order to avoid imposing an logging framework on the end-user of the component or library. - He or she may choose the desired logging framework at deployment - time by inserting the desired slf4j binding on the classpath, - which may be changed later by replacing an existing binding with - another on the class path and restarting the application. This - approach has proven to be simple and very robust. + Thus, the end-user may choose the desired logging framework at + deployment time by inserting the corresponding slf4j binding on + the classpath, which may be changed later by replacing an + existing binding with another on the class path and restarting + the application. This approach has proven to be simple and very + robust. </p> <p><b>As of SLF4J version 1.6.0</b>, if no binding is found on the class path, then 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 + throwing a <code>NoClassDefFoundError</code> because the + <code>org.slf4j.impl.StaticLoggerBinder</code> class is missing, + SLF4J version 1.6.0 and later will emit a single warning message about the absence of a binding and proceed to discard all log requests without further protest. For example, let Wombat be some biology-related framework depending on SLF4J for @@ -220,8 +223,9 @@ public class HelloWorld { but no binding. Even in the absence of any SLF4J binding on the class path, Wombat's distribution will still work out-of-the-box, and without requiring the end-user to download a - binding from SLF4J's web-site. Only when the end-user wishes to - enable logging will she need to install a binding. + binding from SLF4J's web-site. Only when the end-user decides to + enable logging will she need to install the SLF4J binding + corresponding to the logging framework chosen by the end-user. </p> <h3><a name="consolidate" href="#consolidate">Consolidate ----------------------------------------------------------------------- Summary of changes: slf4j-site/src/site/pages/codes.html | 19 +++++++++---------- slf4j-site/src/site/pages/faq.html | 32 +++++++++++++------------------- slf4j-site/src/site/pages/manual.html | 26 +++++++++++++++----------- 3 files changed, 37 insertions(+), 40 deletions(-) hooks/post-receive -- SLF4J: Simple Logging Facade for Java

1 0

[Bug 189] New: 1.6.0: There is no site/ apidocs directory in the distribution zip file.
by bugzilla-daemon＠pixie.qos.ch 05 Jul '10

05 Jul '10

http://bugzilla.slf4j.org/show_bug.cgi?id=189 Summary: 1.6.0: There is no site/apidocs directory in the distribution zip file. Product: SLF4J Version: unspecified Platform: PC OS/Version: All Status: NEW Severity: major Priority: P1 Component: Unspecified AssignedTo: slf4j-dev(a)qos.ch ReportedBy: alex-pub.slf4j(a)reflexion.net slf4j-1.6.0.zip from the distribution directory does not contain 'site/apidocs' directory. The previous stable distribution sfl4j-1.5.8.zip contains this directory. -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 6

Release of SLF4J version 1.6.1
by Ceki Gülcü 05 Jul '10

05 Jul '10

Hello all, I am happy to announce the immediate availability of SLF4J version 1.6.1 consisting bug fixes and dependency updates. 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://qos.ch/mailman/listinfo/announce -- Ceki Gülcü Logback: The reliable, fast and flexible logging framework for Java. http://logback.qos.ch

1 0

[GIT] SLF4J: Simple Logging Facade for Java annotated tag, v_1.6.1, created. v_1.6.1
by git-noreply＠pixie.qos.ch 05 Jul '10

05 Jul '10

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 annotated tag, v_1.6.1 has been created at 96b7f5b90f493feb1891f60cc0fe62aad0b00a39 (tag) tagging 990f24180a7fe18040a851a71f6fab06a4f18604 (commit) replaces v_1.6.0 tagged by Ceki Gulcu on Mon Jul 5 22:28:42 2010 +0200 - Log ----------------------------------------------------------------- tagging as 1.6.1 Ceki Gulcu (4): - starting work on 1.6.1 - we use log4j version 1.2.14 - update to the latest versions of log4j and cal10n - preparing release 1.6.1 ----------------------------------------------------------------------- hooks/post-receive -- SLF4J: Simple Logging Facade for Java

1 0

[GIT] SLF4J: Simple Logging Facade for Java branch, master, updated. v_1.6.0-4-g990f241
by git-noreply＠pixie.qos.ch 05 Jul '10

05 Jul '10

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 990f24180a7fe18040a851a71f6fab06a4f18604 (commit) from 86776fffddd8200782dc57bc2859246b3d592f0c (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=990f24180a7fe18040a851a71f… http://github.com/ceki/slf4j/commit/990f24180a7fe18040a851a71f6fab06a4f18604 commit 990f24180a7fe18040a851a71f6fab06a4f18604 Author: Ceki Gulcu <ceki(a)qos.ch> Date: Mon Jul 5 22:26:53 2010 +0200 - preparing release 1.6.1 - Updated log4j dependency to version 1.2.16 and CAL10N dependency to version 0.7.4. diff --git a/integration/pom.xml b/integration/pom.xml index fa87087..fa9f14e 100644 --- a/integration/pom.xml +++ b/integration/pom.xml @@ -6,7 +6,7 @@ <parent> <groupId>org.slf4j</groupId> <artifactId>slf4j-parent</artifactId> - <version>1.6.1-SNAPSHOT</version> + <version>1.6.1</version> </parent> <modelVersion>4.0.0</modelVersion> diff --git a/jcl-over-slf4j/pom.xml b/jcl-over-slf4j/pom.xml index e612e29..cec9873 100644 --- a/jcl-over-slf4j/pom.xml +++ b/jcl-over-slf4j/pom.xml @@ -3,7 +3,7 @@ <parent> <groupId>org.slf4j</groupId> <artifactId>slf4j-parent</artifactId> - <version>1.6.1-SNAPSHOT</version> + <version>1.6.1</version> </parent> <modelVersion>4.0.0</modelVersion> diff --git a/jul-to-slf4j/pom.xml b/jul-to-slf4j/pom.xml index 0a8c715..cd8d598 100644 --- a/jul-to-slf4j/pom.xml +++ b/jul-to-slf4j/pom.xml @@ -6,7 +6,7 @@ <parent> <groupId>org.slf4j</groupId> <artifactId>slf4j-parent</artifactId> - <version>1.6.1-SNAPSHOT</version> + <version>1.6.1</version> </parent> <modelVersion>4.0.0</modelVersion> diff --git a/log4j-over-slf4j/pom.xml b/log4j-over-slf4j/pom.xml index 68027d0..434199b 100644 --- a/log4j-over-slf4j/pom.xml +++ b/log4j-over-slf4j/pom.xml @@ -5,7 +5,7 @@ <parent> <groupId>org.slf4j</groupId> <artifactId>slf4j-parent</artifactId> - <version>1.6.1-SNAPSHOT</version> + <version>1.6.1</version> </parent> <modelVersion>4.0.0</modelVersion> diff --git a/osgi-over-slf4j/pom.xml b/osgi-over-slf4j/pom.xml index f4054ff..6a18c58 100644 --- a/osgi-over-slf4j/pom.xml +++ b/osgi-over-slf4j/pom.xml @@ -3,7 +3,7 @@ <parent> <groupId>org.slf4j</groupId> <artifactId>slf4j-parent</artifactId> - <version>1.6.1-SNAPSHOT</version> + <version>1.6.1</version> </parent> <modelVersion>4.0.0</modelVersion> diff --git a/pom.xml b/pom.xml index a3e7c9c..3ec46bd 100644 --- a/pom.xml +++ b/pom.xml @@ -5,7 +5,7 @@ <groupId>org.slf4j</groupId> <artifactId>slf4j-parent</artifactId> - <version>1.6.1-SNAPSHOT</version> + <version>1.6.1</version> <packaging>pom</packaging> <name>SLF4J</name> diff --git a/slf4j-api/pom.xml b/slf4j-api/pom.xml index 6d65557..e4e9b65 100644 --- a/slf4j-api/pom.xml +++ b/slf4j-api/pom.xml @@ -5,7 +5,7 @@ <parent> <groupId>org.slf4j</groupId> <artifactId>slf4j-parent</artifactId> - <version>1.6.1-SNAPSHOT</version> + <version>1.6.1</version> </parent> <modelVersion>4.0.0</modelVersion> diff --git a/slf4j-ext/pom.xml b/slf4j-ext/pom.xml index a366dab..1e31a77 100644 --- a/slf4j-ext/pom.xml +++ b/slf4j-ext/pom.xml @@ -5,7 +5,7 @@ <parent> <groupId>org.slf4j</groupId> <artifactId>slf4j-parent</artifactId> - <version>1.6.1-SNAPSHOT</version> + <version>1.6.1</version> </parent> <modelVersion>4.0.0</modelVersion> diff --git a/slf4j-jcl/pom.xml b/slf4j-jcl/pom.xml index 1fac3e3..fdfbc8f 100644 --- a/slf4j-jcl/pom.xml +++ b/slf4j-jcl/pom.xml @@ -3,7 +3,7 @@ <parent> <groupId>org.slf4j</groupId> <artifactId>slf4j-parent</artifactId> - <version>1.6.1-SNAPSHOT</version> + <version>1.6.1</version> </parent> <modelVersion>4.0.0</modelVersion> diff --git a/slf4j-jdk14/pom.xml b/slf4j-jdk14/pom.xml index 0214e5d..2e4a3f4 100644 --- a/slf4j-jdk14/pom.xml +++ b/slf4j-jdk14/pom.xml @@ -6,7 +6,7 @@ <parent> <groupId>org.slf4j</groupId> <artifactId>slf4j-parent</artifactId> - <version>1.6.1-SNAPSHOT</version> + <version>1.6.1</version> </parent> <modelVersion>4.0.0</modelVersion> diff --git a/slf4j-log4j12/pom.xml b/slf4j-log4j12/pom.xml index 972793b..6953e5c 100644 --- a/slf4j-log4j12/pom.xml +++ b/slf4j-log4j12/pom.xml @@ -6,7 +6,7 @@ <parent> <groupId>org.slf4j</groupId> <artifactId>slf4j-parent</artifactId> - <version>1.6.1-SNAPSHOT</version> + <version>1.6.1</version> </parent> <modelVersion>4.0.0</modelVersion> diff --git a/slf4j-migrator/pom.xml b/slf4j-migrator/pom.xml index 73c2585..31237d7 100644 --- a/slf4j-migrator/pom.xml +++ b/slf4j-migrator/pom.xml @@ -7,7 +7,7 @@ <parent> <groupId>org.slf4j</groupId> <artifactId>slf4j-parent</artifactId> - <version>1.6.1-SNAPSHOT</version> + <version>1.6.1</version> </parent> <modelVersion>4.0.0</modelVersion> diff --git a/slf4j-nop/pom.xml b/slf4j-nop/pom.xml index 5c02fd4..1eaf1b1 100644 --- a/slf4j-nop/pom.xml +++ b/slf4j-nop/pom.xml @@ -6,7 +6,7 @@ <parent> <groupId>org.slf4j</groupId> <artifactId>slf4j-parent</artifactId> - <version>1.6.1-SNAPSHOT</version> + <version>1.6.1</version> </parent> <modelVersion>4.0.0</modelVersion> diff --git a/slf4j-osgi-integration-test/pom.xml b/slf4j-osgi-integration-test/pom.xml index 7826e90..4f9c606 100644 --- a/slf4j-osgi-integration-test/pom.xml +++ b/slf4j-osgi-integration-test/pom.xml @@ -6,7 +6,7 @@ <parent> <groupId>org.slf4j</groupId> <artifactId>slf4j-parent</artifactId> - <version>1.6.1-SNAPSHOT</version> + <version>1.6.1</version> </parent> <modelVersion>4.0.0</modelVersion> diff --git a/slf4j-osgi-test-bundle/pom.xml b/slf4j-osgi-test-bundle/pom.xml index 75d5fac..fe85a98 100644 --- a/slf4j-osgi-test-bundle/pom.xml +++ b/slf4j-osgi-test-bundle/pom.xml @@ -6,7 +6,7 @@ <parent> <groupId>org.slf4j</groupId> <artifactId>slf4j-parent</artifactId> - <version>1.6.1-SNAPSHOT</version> + <version>1.6.1</version> </parent> <modelVersion>4.0.0</modelVersion> diff --git a/slf4j-simple/pom.xml b/slf4j-simple/pom.xml index fa6ae43..3275f44 100644 --- a/slf4j-simple/pom.xml +++ b/slf4j-simple/pom.xml @@ -3,7 +3,7 @@ <parent> <groupId>org.slf4j</groupId> <artifactId>slf4j-parent</artifactId> - <version>1.6.1-SNAPSHOT</version> + <version>1.6.1</version> </parent> <modelVersion>4.0.0</modelVersion> diff --git a/slf4j-site/pom.xml b/slf4j-site/pom.xml index dd91df9..fb1b2f7 100644 --- a/slf4j-site/pom.xml +++ b/slf4j-site/pom.xml @@ -5,7 +5,7 @@ <parent> <groupId>org.slf4j</groupId> <artifactId>slf4j-parent</artifactId> - <version>1.6.1-SNAPSHOT</version> + <version>1.6.1</version> </parent> <modelVersion>4.0.0</modelVersion> diff --git a/slf4j-site/src/site/pages/download.html b/slf4j-site/src/site/pages/download.html index b3c8eae..de39fed 100644 --- a/slf4j-site/src/site/pages/download.html +++ b/slf4j-site/src/site/pages/download.html @@ -59,6 +59,13 @@ href="dist/">main repository</a>. </p> + <h3>javadoc downloads</h3> + + <p>For each slf4j module, the corresponding javadoc artifacts can be + downloaded from the <a + href="http://repo2.maven.org/maven2/org/slf4j/">Maven central + repository</a> as <em>javadoc.jar</em> files. + </p> <h2>Additional SLF4J-related software</h2> diff --git a/slf4j-site/src/site/pages/news.html b/slf4j-site/src/site/pages/news.html index 323ae67..d42b4d4 100644 --- a/slf4j-site/src/site/pages/news.html +++ b/slf4j-site/src/site/pages/news.html @@ -29,7 +29,12 @@ <hr noshade="noshade" size="1"/> - <h3>, 2010 - Release of SLF4J 1.6.1</h3> + <h3>July 5th, 2010 - Release of SLF4J 1.6.1</h3> + + <p>Updated log4j dependency to version 1.2.16 and <a + href="http://cal10n.qos.ch/">CAL10N</a> dependency to version + 0.7.4. + </p> <p>Fixed missing versioning OSGi metadata in the log4j-over-slf4j module. This problem was reported in <a @@ -37,6 +42,8 @@ David Savage. </p> + + <hr noshade="noshade" size="1"/> <h3>May 8th, 2010 - Release of SLF4J 1.6.0</h3> ----------------------------------------------------------------------- Summary of changes: integration/pom.xml | 2 +- jcl-over-slf4j/pom.xml | 2 +- jul-to-slf4j/pom.xml | 2 +- log4j-over-slf4j/pom.xml | 2 +- osgi-over-slf4j/pom.xml | 2 +- pom.xml | 2 +- slf4j-api/pom.xml | 2 +- slf4j-ext/pom.xml | 2 +- slf4j-jcl/pom.xml | 2 +- slf4j-jdk14/pom.xml | 2 +- slf4j-log4j12/pom.xml | 2 +- slf4j-migrator/pom.xml | 2 +- slf4j-nop/pom.xml | 2 +- slf4j-osgi-integration-test/pom.xml | 2 +- slf4j-osgi-test-bundle/pom.xml | 2 +- slf4j-simple/pom.xml | 2 +- slf4j-site/pom.xml | 2 +- slf4j-site/src/site/pages/download.html | 7 +++++++ slf4j-site/src/site/pages/news.html | 9 ++++++++- 19 files changed, 32 insertions(+), 18 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.0-3-g86776ff
by git-noreply＠pixie.qos.ch 05 Jul '10

05 Jul '10

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 86776fffddd8200782dc57bc2859246b3d592f0c (commit) from 1db99e3cbe2b997bf54a8fb13b5692adfdc0df84 (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=86776fffddd8200782dc57bc28… http://github.com/ceki/slf4j/commit/86776fffddd8200782dc57bc2859246b3d592f0c commit 86776fffddd8200782dc57bc2859246b3d592f0c Author: Ceki Gulcu <ceki(a)qos.ch> Date: Mon Jul 5 19:55:43 2010 +0200 - update to the latest versions of log4j and cal10n diff --git a/pom.xml b/pom.xml index b4306f1..a3e7c9c 100644 --- a/pom.xml +++ b/pom.xml @@ -28,8 +28,8 @@ <properties> <slf4j.api.minimum.compatible.version>1.6.0</slf4j.api.minimum.compatible.version> - <cal10n.version>0.7.2</cal10n.version> - <log4j.version>1.2.14</log4j.version> + <cal10n.version>0.7.4</cal10n.version> + <log4j.version>1.2.16</log4j.version> </properties> ----------------------------------------------------------------------- Summary of changes: pom.xml | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) hooks/post-receive -- SLF4J: Simple Logging Facade for Java

1 0

Re: [slf4j-dev] Context for getLogger()
by Fred 02 Jul '10

02 Jul '10

I have been modifying slf4j for use on android. Beginning with the slf4j-android sub-project, I am adding in a context provider to record, forward, combine, filter and otherwise manage the log. In order to do this getLogger needs to know the current context. To work around this I have added a context parameter. e.g. import android.content.Context; import android.graphics.Matrix; import org.slf4j.Logger; import org.slf4j.LoggerFactory; public class Sample implements Cloneable { private Sample(Context context) { _log = LoggerFactory.getLogger(Sample.class, context); ... I can provide more detail if this is not clear. What I want to know is if this is the best way do deal with the problem? In order to get this to work I have added some android specific stuff to the api/contract. The presumption seems to be that certain information is in some global variable. This doesn't seem quite right. What I am wondering is if there shouldn't be some generalization of context for slf4j. The specific implementation would change it as needed. What do you think?

2 4

[Bug 188] New: There is no 1.6.x version in a dropdown list.
by bugzilla-daemon＠pixie.qos.ch 30 Jun '10

30 Jun '10

http://bugzilla.slf4j.org/show_bug.cgi?id=188 Summary: There is no 1.6.x version in a dropdown list. Product: SLF4J Version: 1.5.x Platform: PC OS/Version: Windows XP Status: NEW Severity: blocker Priority: P1 Component: Unspecified AssignedTo: slf4j-dev(a)qos.ch ReportedBy: alex-pub.slf4j(a)reflexion.net Summary says it all. -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 1

[Bug 187] New: OSGi meta data in 1.6
by bugzilla-daemon＠pixie.qos.ch 30 Jun '10

30 Jun '10

http://bugzilla.slf4j.org/show_bug.cgi?id=187 Summary: OSGi meta data in 1.6 Product: SLF4J Version: unspecified Platform: All OS/Version: All Status: NEW Severity: normal Priority: P1 Component: log4j-over-slf4j AssignedTo: slf4j-dev(a)qos.ch ReportedBy: davemssavage(a)googlemail.com I'm working on integrating slf4j 1.6 in an osgi environment and have hit a stumbling block using the log4j-over-slf4j legacy support. The bundle exports the org.apache.log4j package using the default version (0.0.0) this causes problems when client code tries to use these packages if they declare an explicit import version range - in our case the imports are: Import-Package: org.apache.log4j;version=[1.2.14,1.3) 0.0.0 is not in the range 1.2.14->1.3 In my environment I've rebuilt the log4j-over-slf4j bundle with the following manifest which fixes the problem: $ cat log4j-over-slf4j/src/main/resources/META-INF/MANIFEST.MF Implementation-Title: log4j-over-slf4j Bundle-SymbolicName: log4j.over.slf4j Bundle-Name: log4j-over-slf4j Bundle-Vendor: SLF4J.ORG Export-Package: org.apache.log4j;version=1.2.14 Import-Package: org.slf4j, org.slf4j.helpers, org.slf4j.spi However I'm just taking a wild guess that 1.2.14 is the version of the log4j api that this bundle provides. -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 1