April 2012 - slf4j-dev - mailman3.qos.ch

[Bug 236] New: Use standard java.util.ServiceLoader for SLF4J Binding
by bugzilla-daemon＠pixie.qos.ch 25 Feb '13

25 Feb '13

http://bugzilla.slf4j.org/show_bug.cgi?id=236 Summary: Use standard java.util.ServiceLoader for SLF4J Binding Product: SLF4J Version: unspecified Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P1 Component: Core API AssignedTo: slf4j-dev(a)qos.ch ReportedBy: cronier.jy(a)gmail.com What about use ServiceLoader to find which binding to use? For JDK<1.6 compatibility, we can test Class.forName("java.util.ServiceLoader") and switch to an internal equivalent implementation of ServiceLoader. No need to have one (or multiple) StaticLoggerBinder. This ServiceLoader is used, for example, for JRE XSL implementation, or java.sql.Driver. -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

2 10

[Bug 218] New: Broken link on website
by bugzilla-daemon＠pixie.qos.ch 21 Sep '12

21 Sep '12

http://bugzilla.slf4j.org/show_bug.cgi?id=218 Summary: Broken link on website Product: SLF4J Version: unspecified Platform: All OS/Version: All Status: NEW Severity: trivial Priority: P1 Component: Unspecified AssignedTo: slf4j-dev(a)qos.ch ReportedBy: cowwoc(a)bbs.darktech.org The nabble links found at http://www.slf4j.org/mailing-lists.html point to deleted forums. Please recreate the forums. -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

2 1

[Bug 220] New: Cannot build slf4j from source - missing osgi-build.xml
by bugzilla-daemon＠pixie.qos.ch 09 Aug '12

09 Aug '12

http://bugzilla.slf4j.org/show_bug.cgi?id=220 Summary: Cannot build slf4j from source - missing osgi-build.xml Product: SLF4J Version: 1.6.x Platform: PC OS/Version: Windows XP Status: NEW Severity: blocker Priority: P1 Component: Unspecified AssignedTo: slf4j-dev(a)qos.ch ReportedBy: dick.jones(a)kinetx.com I tried to build slf4j 1.6.1 from source and the build failed with the following error: org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.2:run (ant-osgi-test) on project integration: An Ant BuildException has occured: The following error occurred while executing this line: java.io.FileNotFoundException: C:\Users\dick.jones.KINETX\Downloads\slf4j-1.6.1\integration\osgi-build.xml (The system cannot find the file specified) I emailed Ceki Gulcu who said the file, osgi-build.xml, was inadvertently ommitted and asked that I enter this as a bug. -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

2 1

[Bug 186] New: [patch] Enhanced SimpleLogger implementation
by bugzilla-daemon＠pixie.qos.ch 12 Jun '12

12 Jun '12

http://bugzilla.slf4j.org/show_bug.cgi?id=186 Summary: [patch] Enhanced SimpleLogger implementation Product: SLF4J Version: unspecified Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P2 Component: Implementations AssignedTo: slf4j-dev(a)qos.ch ReportedBy: cedrik.lime(a)gmail.com Created an attachment (id=70) --> (http://bugzilla.slf4j.org/attachment.cgi?id=70) New implementation of SimpleLogger I recently had to enhance SimpleLogger by back-porting some functionalities of commons-logging's SimpleLog into it. Namely, I have added the following: * optional configuration file; if none found, you get the exact same set of features as the currently released SimpleLogger. * enable to log more than the info log level * enable to set different log levels for different Loggers * enable to show/hide thread name * very primitive log messages customisation (about the same as commons-logging) Once again, the new code is totally compatible in behaviour and output with the currently released SimpleLogger. I also made it so that current users of commons-logging can upgrade to SLF4J very easily. Finally, I made sure to keep SimpleLogger as simple as possible: we already have fully-fledged logging frameworks, let's not re-invent one! I think this new implementation would enhance the value of SLF4J, while keeping a perfect retro-compatibility with previous versions. -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

2 11

[Bug 234] New: log4j-over-slf4j and legacy projects providing their own log4j LoggerFactory
by bugzilla-daemon＠pixie.qos.ch 04 Jun '12

04 Jun '12

http://bugzilla.slf4j.org/show_bug.cgi?id=234 Summary: log4j-over-slf4j and legacy projects providing their own log4j LoggerFactory Product: SLF4J Version: 1.6.x Platform: All OS/Version: All Status: NEW Severity: blocker Priority: P1 Component: log4j-over-slf4j AssignedTo: slf4j-dev(a)qos.ch ReportedBy: laurent.pellegrino(a)gmail.com I tried to use log4j-over-slf4j in a legacy project that provides its own LoggerFactory and when I use log4j-over-slf4j I get a java.lang.NoSuchMethodError for Logger#getLogger(String name, LoggerFactory factory). After having inspected the log4j-over-slf4j source code, it seems that the bridge does not provide an implementation for the Logger#getLogger(String name, LoggerFactory factory) method. Is there any reason for that? -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

2 5

[Bug 219] New: Typo in error message
by bugzilla-daemon＠pixie.qos.ch 19 Apr '12

19 Apr '12

http://bugzilla.slf4j.org/show_bug.cgi?id=219 Summary: Typo in error message Product: SLF4J Version: 1.6.x Platform: PC OS/Version: Windows NT Status: NEW Severity: blocker Priority: P1 Component: Core API AssignedTo: slf4j-dev(a)qos.ch ReportedBy: cowwoc(a)bbs.darktech.org Replace "becasue" with "because" across the slf4j code-base. I got this specific error message: SLF4J: The following loggers will not work becasue they were created SLF4J: during the default configuration phase of the underlying logging system. SLF4J: See also http://www.slf4j.org/codes.html#substituteLogger -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

2 2

Commencez à faire des profits avec les options binaires
by unknown＠example.com 19 Apr '12

19 Apr '12

1 0

*****SPAM***** Trader le pétrole maintenant et faites 81%de profits
by unknown＠example.com 19 Apr '12

19 Apr '12

Spam detection software, running on the system "pixie", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: Plus de 85% de profit en moins d' 1 heure Facile comme 1, 2, 3 Choisissez l'actif a trader Cliquez "CALL" si vous pensez que le prix va monter Cliquez "PUT" si vous pensez que le prix va baisser [...] Content analysis details: (6.3 points, 5.7 required) pts rule name description ---- ---------------------- -------------------------------------------------- 0.0 HTML_MESSAGE BODY: HTML included in message 0.8 BAYES_50 BODY: Bayes spam probability is 40 to 60% [score: 0.4938] 0.7 MIME_HTML_ONLY BODY: Message only has text/html MIME parts 1.1 HTML_IMAGE_ONLY_16 BODY: HTML: images with 1200-1600 bytes of words 0.4 RCVD_IN_XBL RBL: Received via a relay in Spamhaus XBL [190.137.162.4 listed in zen.spamhaus.org] 1.4 RCVD_IN_BRBL_LASTEXT RBL: RCVD_IN_BRBL_LASTEXT [190.137.162.4 listed in bb.barracudacentral.org] 0.5 MISSING_MID Missing Message-Id: header 1.4 MISSING_DATE Missing Date: header 0.0 T_REMOTE_IMAGE Message contains an external image The original message was not completely plain text, and may be unsafe to open with some email clients; in particular, it may contain a virus, or confirm that your address can receive spam. If you wish to view it, it may be safer to save it to a file and open it with an editor.

1 0

[GIT] SLF4J: Simple Logging Facade for Java branch master updated. v_1.6.4-10-gff5860e
by git-noreply＠pixie.qos.ch 14 Apr '12

14 Apr '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 ff5860ee622f1c49c60492e0a8a0978905f0a1d6 (commit) from dc204d9a9bcf49e543d7a07392e0cd958f4700f4 (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=ff5860ee622f1c49c60492e0a8… http://github.com/ceki/slf4j/commit/ff5860ee622f1c49c60492e0a8a0978905f0a1d6 commit ff5860ee622f1c49c60492e0a8a0978905f0a1d6 Author: Ceki Gulcu <ceki(a)qos.ch> Date: Sat Apr 14 19:45:59 2012 +0200 link to ohloh usuage (in footer.js) + edits (in legacy.html) diff --git a/slf4j-site/src/site/pages/legacy.html b/slf4j-site/src/site/pages/legacy.html index 4fb5817..866f1b9 100644 --- a/slf4j-site/src/site/pages/legacy.html +++ b/slf4j-site/src/site/pages/legacy.html @@ -220,12 +220,13 @@ process incurs the cost of constructing a <code>LogRecord</code> instance regardless of whether the SLF4J logger is disabled for the given level or nor. <b>Consequently, j.u.l. to SLF4J - translation can seriously impact on the cost of disabled logging - statements (60 fold increase) and a measurable impact on enabled - log statements (20% overall increase).</b> Please note that as of - logback-version 0.9.25, it is possible to completely eliminate the - 60 fold translation overhead for disabled log statements with the - help of <a + translation can seriously increase the cost of disabled logging + statements (60 fold or 6000% increase) and + measurably impact the performance of enabled log statements (20% + overall increase).</b> Please note that as of logback-version + 0.9.25, it is possible to completely eliminate the 60 fold + translation overhead for disabled log statements with the help of + <a href="http://logback.qos.ch/manual/configuration.html#LevelChangePropagator">LevelChangePropagator</a>. </p> diff --git a/slf4j-site/src/site/pages/templates/footer.js b/slf4j-site/src/site/pages/templates/footer.js index 4d75cfd..db27372 100644 --- a/slf4j-site/src/site/pages/templates/footer.js +++ b/slf4j-site/src/site/pages/templates/footer.js @@ -1,18 +1,25 @@ -document.write('<table class="footer">') +document.write('<table class="footer" border="0">') document.write('<tr>') -document.write(' <td>') +document.write(' <td valign="top" align="left">Copyright © 2004-2012 <a href="http://www.qos.ch/">QOS.ch</a></td>') -//document.write(' <a href="http://validator.w3.org/check?uri=referer">') -//document.write(' <img align="left" src="http://www.w3.org/Icons/valid-xhtml10"') -//document.write(' alt="Valid XHTML 1.0 Transitional" height="31" width="88" /></a>') -document.write(' </td>') - -document.write('<td valign="top">Copyright © 2004-2012 <a href="http://www.qos.ch/">QOS.ch</a></td>') +document.write(' <td align="right" rowspan="2">') +document.write(' <script type="text/javascript" src="http://www.ohloh.net/p/11217/widgets/project_users.js"></script>') +document.write(' </td>') +document.write('</tr>') +AAT = '@' +DOOTT = '.' +document.write('<tr>') +document.write('<td align="left" colspan="1">') +document.write('We are actively looking for volunteers to proofread the documentation. Please send your corrections or suggestions for improvement to "corrections' + AAT +'qos'+DOOTT+'ch". See also the <a href="http://articles.qos.ch/contributing.html">instructions for contributors</a>.'); +document.write('</td>') +document.write(' <td> </td>') document.write('</tr>') + + document.write('</table>') ----------------------------------------------------------------------- Summary of changes: slf4j-site/src/site/pages/legacy.html | 13 +++++++------ slf4j-site/src/site/pages/templates/footer.js | 23 +++++++++++++++-------- 2 files changed, 22 insertions(+), 14 deletions(-) hooks/post-receive -- SLF4J: Simple Logging Facade for Java

1 0

Add a third parameter of the log API if possible
by George Cao 11 Apr '12

11 Apr '12

Hi guys, I use slf4j log API for long time, one thing i feel inconvenience about it the default number of log API parameters is 2. For instance: public void warn(String format, Object arg1, Object arg2); Usually i log something in the 'who did what, and result is what ' style. e.g. LOG.info("User {} update post {}, result is {}", userId, postId, true); but the max number of parameters of this API is 2, so i need to write it like this: LOG.info("User {} update post {}, result is {}",new Object[]{ userId, postId, true}); I think the number of parameters of this API should be 3 and 3 is the most common cases for a meaning log info. Is this true or what are your concerns when you design the APIs? Best regards, George

2 1