September 2011 - 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

[Bug 246] New: EventLogger.logEvent() does not pass the EventData as an object.
by bugzilla-daemon＠pixie.qos.ch 28 Sep '11

28 Sep '11

http://bugzilla.slf4j.org/show_bug.cgi?id=246 Summary: EventLogger.logEvent() does not pass the EventData as an object. Product: SLF4J Version: 1.6.x Platform: PC OS/Version: Mac OS X 10.3 Status: NEW Severity: critical Priority: P1 Component: slf4j-ext AssignedTo: slf4j-dev(a)qos.ch ReportedBy: rgoers(a)apache.org When this was first written LocationAwareLogger did not support passing objects. When it was modified EventLogger should have been modified to pass the EventData as an object but instead passes a null. logEvent should be modified as: public static void logEvent(EventData data) { if (eventLogger.instanceofLAL) { ((LocationAwareLogger) eventLogger.logger).log(EVENT_MARKER, FQCN, LocationAwareLogger.INFO_INT, data.toXML(), new Object[] {data}, null); } else { eventLogger.logger.info(EVENT_MARKER, data.toXML(), data); } } -- 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

[GIT] SLF4J: Simple Logging Facade for Java branch, master, updated. v_1.6.2-2-g98af61a
by git-noreply＠pixie.qos.ch 28 Sep '11

28 Sep '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 98af61a76ecf4a5ba04d3877267c9f33d477ee30 (commit) from 13dddd52b72ac1c3bd2971d5c30a6f66cfae47ca (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=98af61a76ecf4a5ba04d387726… http://github.com/ceki/slf4j/commit/98af61a76ecf4a5ba04d3877267c9f33d477ee30 commit 98af61a76ecf4a5ba04d3877267c9f33d477ee30 Author: Ceki Gulcu <ceki(a)qos.ch> Date: Wed Sep 28 20:01:45 2011 +0200 fixes bug 246 diff --git a/slf4j-ext/src/main/java/org/slf4j/ext/EventLogger.java b/slf4j-ext/src/main/java/org/slf4j/ext/EventLogger.java index 2f77c1b..9fba219 100755 --- a/slf4j-ext/src/main/java/org/slf4j/ext/EventLogger.java +++ b/slf4j-ext/src/main/java/org/slf4j/ext/EventLogger.java @@ -34,7 +34,7 @@ public class EventLogger { public static void logEvent(EventData data) { if (eventLogger.instanceofLAL) { ((LocationAwareLogger) eventLogger.logger).log(EVENT_MARKER, FQCN, - LocationAwareLogger.INFO_INT, data.toXML(), null, null); + LocationAwareLogger.INFO_INT, data.toXML(), new Object[] {data}, null); } else { eventLogger.logger.info(EVENT_MARKER, data.toXML(), data); } diff --git a/slf4j-site/src/site/pages/news.html b/slf4j-site/src/site/pages/news.html index acb6f1c..99ddd76 100644 --- a/slf4j-site/src/site/pages/news.html +++ b/slf4j-site/src/site/pages/news.html @@ -29,8 +29,16 @@ <hr noshade="noshade" size="1"/> - <h3>August 19th, 2011 - Release of SLF4J 1.6.2</h3> + <h3>???, 2011 - Release of SLF4J 1.6.3</h3> + + <p><code>LogEvent</code> class in slf4j-ext module now correctly + passes the event data as a parameter object. This fixes <a + href="http://bugzilla.slf4j.org/show_bug.cgi?id=246">bug #246</a> + reported by Ralph Goers. + </p> + + <h3>August 19th, 2011 - Release of SLF4J 1.6.2</h3> <p>Fixed <a href="http://bugzilla.slf4j.org/show_bug.cgi?id=138">bug ----------------------------------------------------------------------- Summary of changes: .../src/main/java/org/slf4j/ext/EventLogger.java | 2 +- slf4j-site/src/site/pages/news.html | 10 +++++++++- 2 files changed, 10 insertions(+), 2 deletions(-) hooks/post-receive -- SLF4J: Simple Logging Facade for Java

1 0

updated 2.0 proposal
by John Vasileff 17 Sep '11

17 Sep '11

I pushed updates to github taking into account much of the feedback I received. The updated code has the following: 1) Simplified 2.0 API for logger and adapter writers. The idea is to make it much easier to write adapters/loggers and reduce risk of bugs by removing application facing API specifics such as formatting and Logger method signatures from adapter/logger implementations. Future enhancements to Logger may be made with less concern about breaking binary compatibility. 2) Maintain binary compatibility with all pre 2.0 adapters while not restricting future additions to the Logger interface. New Logger methods will work with old adapters. The tradeoff is that old loggers will not have access to the raw messagePattern - LocationAwareLogger does not support this. Non LocationAwareLoggers will not have access to the message parameters. So, Logback filtering on the raw messagePattern (using a pre 2.0 compatible logback) will be slightly less accurate, but it will be no worse than in 1.6 when using a wrapper such as XLogger. New 2.0 style loggers and adapters should have a maven dependency for the 2.0 slf4j-api. This will in no way break existing apps that for whatever reason may also bring in "other" 1.6 components as long as the app is compiled and deployed on Java 5+. 3) Addition of log Entry objects similar to Message objects that have been discussed. This design does not attempt to unify audit and access log APIs, but otherwise provides all of the capabilities of Message objects with the additional benefit that Entry objects can control Level and Marker. For example, an advanced application writer may have a custom EventEntry class that properly translates domain specific details to Level & Marker, such as map EventType.SECURITY_VIOLATION to Level.WARN, etc. A StructuredData object may accept syslog severities, but automatically translate to the appropriate slf4j Level in order to support adapters that do not understand StructuredData. 4) The log Entry interface is minimal, with additional interfaces adding functionality. Adapters that support additional functionality can use "instanceof". Future version of SLF4J may introduce additional features exposed through new interfaces without breaking compatibility with older adapters. 5) Support for logger.withFormatter(Formatter x) while maintaining Logger immutability and support for pre 2.0 loggers. I am not proposing this be included in the 2.0 API. But I feel that it is valuable to explore how this type of feature (formatting or whatever else may come) could be added to loggers in the future while the 2.0 API is being worked out. 6) I removed supplementalData and the numerous arg1...arg6 methods. I agree with Joern that it is probably best to avoid Google Collections style methods given the relatively low cost of implicit Object[] creation. There may be some value to supplementalData, but under this 2.0 proposal, it could be added any time in the future, so no use worrying about it now. Disclaimers - Unit tests pass with both 1.6 and 2.0 style adapters, but I haven't fully tested them for things like FQCN. And, of course, claims of binary compatibility while introducing features are nothing more than theory until fully tested. - A new interface LoggingProvider specifies what must be implemented for 2.0 style adapters. But, adapters still also implement Logger by extending AbstractLogger. The class hierarchy and clarity may be better if 2.0 adapters simply implemented LoggingProvider with a LoggerImpl created by LoggerFactory. - Legacy adapters are wrapped each time they are created. It may be better to cache them in LoggerFactory with a WeakHashMap<[old]Logger, WeakReference<[wrapped]Logger>> to save some cycles and GC. - Class naming and package structure needs some work - LoggingProvider, Level, Entry and various Entry sub interfaces, etc. - deserialization needs work. The new code is available at https://github.com/jvasileff/slf4j/tree/topic-jdk5-varargs An additional test branch that reverts all adapters, XLogger, and EventLogger to 1.6.2 source for basic compatibility testing is available at https://github.com/jvasileff/slf4j/tree/topic-jdk5-legacy-adapter-test John

2 5

[Bug 245] New: incorrect isTraceEnabled call in XLogger
by bugzilla-daemon＠pixie.qos.ch 16 Sep '11

16 Sep '11

http://bugzilla.slf4j.org/show_bug.cgi?id=245 Summary: incorrect isTraceEnabled call in XLogger Product: SLF4J Version: 1.6.x Platform: PC OS/Version: Mac OS X 10.3 Status: NEW Severity: major Priority: P1 Component: slf4j-ext AssignedTo: slf4j-dev(a)qos.ch ReportedBy: git(a)netcc.us public void exit() { if (instanceofLAL && logger.isTraceEnabled(ENTRY_MARKER)) { ((LocationAwareLogger) logger).log(EXIT_MARKER, FQCN, LocationAwareLogger.TRACE_INT, EXIT_MESSAGE_0, null, null); } } should be: ... if (instanceofLAL && logger.isTraceEnabled(EXIT_MARKER)) { ... -- 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