- slf4j-dev - mailman3.qos.ch

slf4j-api and slf4j-android don't play nicely together?
by Carsten.Friedrich＠csiro.au 09 Dec '13

09 Dec '13

I have a library which uses slf4j-api (through maven) and an Android App which uses the library and wants to use slf4j-android. Due to limitation of how maven integration works in Eclipse it seems I can only include all or none of the transitive dependencies of the library in my app. I want to chose all, as I need them (almost) all anyway. However, the classes in slf4j-api and alf4j-android overlap and they both contain copies of classes with identical names. The Android build process in Eclipse does not like this at all: [2013-12-09 16:49:13 - Dex Loader] Unable to execute dex: Multiple dex files define Lorg/slf4j/ILoggerFactory; [2013-12-09 16:49:13 - TSSAndroidColab] Conversion to Dalvik format failed: Unable to execute dex: Multiple dex files define Lorg/slf4j/ILoggerFactory; Is there a way to use a generic base jar in a library and then some other system specific jars (e.g. for Android) in addition without duplicate class definitions? Cheers, Carsten

2 3

[qos-ch/slf4j] 27607e: add link to article [Simplifying the distinction b...
by Ceki Gulcu 27 Nov '13

27 Nov '13

Branch: refs/heads/master Home: https://github.com/qos-ch/slf4j Commit: 27607eafc8ecfd7780c8aa4ac8795aeb2365dc87 https://github.com/qos-ch/slf4j/commit/27607eafc8ecfd7780c8aa4ac8795aeb2365… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2013-11-27 (Wed, 27 Nov 2013) Changed paths: M slf4j-site/src/site/pages/docs.html Log Message: ----------- add link to article [Simplifying the distinction between SL4J and commons logging]

1 0

New Project depending on SLF4J for HTTP Dumping
by Séven Le Mesle 27 Nov '13

27 Nov '13

Hi, I've just released a short oss library that uses SLF4J Api to dump full HttpServletRequest and full HttpServletResponse. The project is on github here : https://github.com/xebia-france/xebia-logfilter-extras It is already synced in maven-central repository, and I wondered wether some of you can be interested in this tool or not. Second question, is: what should I do to get listed in SLF4J home page ? Thanks for your help. Regards -- Séven Le Mesle Xebia IT Architects Email : slemesle(a)xebia.fr Mobile : 06 19 61 81 17 http://www.xebia.fr http://blog.xebia.fr Siège Social La Défense Colisée 10 / 12 Avenue de l'arche Faubourg de l'Arche 92419 Courbevoie Cedex

1 0

[Bug 309] New: Alternative Android implementation
by bugzilla-daemon＠qos.ch 08 Nov '13

08 Nov '13

http://bugzilla.slf4j.org/show_bug.cgi?id=309 Priority: P5 Bug ID: 309 Assignee: slf4j-dev(a)qos.ch Summary: Alternative Android implementation Severity: enhancement Classification: Unclassified OS: Linux Reporter: bugzilla.slf4j.simon(a)arlott.org Hardware: PC Status: NEW Version: 1.7.x Component: slf4j-android Product: SLF4J I've got an alternative implementation of slf4j-android that you may be interested in: https://github.com/lp0/slf4j-android It has various features and configurability (which makes it more of a logging framework than a simple adaptation layer) as the Android logging is quite basic. It avoids the issue in #204 and caches calls to the native isLoggable() method. Minimal configuration to specify a default logging tag is usually required to conform to existing Android conventions (using a minimal number of logger names). -- You are receiving this mail because: You are the assignee for the bug.

1 2

How do you accept code contributions?
by Andreas Magnusson 06 Nov '13

06 Nov '13

Hello all, we're starting to use slf4j at my group in the company and we quickly got bitten by bug 242 (http://bugzilla.slf4j.org/show_bug.cgi?id=242) So instead of just griping about it I want to contribute. But since all open source projects have different rules I thought it best to check here first. So, do I just create branch in Git and issue a push request when I deem myself done? How do I do with licensing? I have a verbal OK from my company but I guess you might need something in writing? Anything else I should think of? Cheers, /Andreas Magnusson

2 1

commons-logging > slf4j > log4j NullPointerException
by jigarjm 03 Nov '13

03 Nov '13

my app is using axis api for some purpose, axis uses commons-logging for logging, I have jcl-over-slf4j to route commons-logging logs to slf4j and I am using log4j binding with slf4j when it attempts to make the instance it throws NullPointerException <code> Caused by: java.lang.NullPointerException at org.apache.log4j.Logger.isTraceEnabled(Logger.java:205) at org.slf4j.impl.Log4jLoggerAdapter.isTraceCapable(Log4jLoggerAdapter.java:83) at org.slf4j.impl.Log4jLoggerAdapter.<init>(Log4jLoggerAdapter.java:78) at org.slf4j.impl.Log4jLoggerFactory.getLogger(Log4jLoggerFactory.java:46) at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:270) at org.apache.commons.logging.impl.SLF4JLogFactory.getInstance(SLF4JLogFactory.java:156) at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:291) at org.apache.axis.components.logger.LogFactory.getLog(LogFactory.java:37) at org.apache.axis.client.Call.<clinit>(Call.java:132) <code> I am using custom Log4jLoggerFactory.java & line 46 is just constructor call with not null logger being passed on Any clue why it is not setting repository in log4j and it leaves it as null I have jcl-over-slfj4 log4j slf4j-api axis in classpath -- View this message in context: http://slf4j.42922.n3.nabble.com/commons-logging-slf4j-log4j-NullPointerExc… Sent from the slf4j - dev mailing list archive at Nabble.com.

1 0

[Bug 75] Cyclic dependency in OSGi
by bugzilla-daemon＠qos.ch 24 Oct '13

24 Oct '13

http://bugzilla.slf4j.org/show_bug.cgi?id=75 --- Comment #18 from Gunnar Wagenknecht <gunnar(a)wagenknecht.org> --- FWIW, it seems that the LOG4J backend implementation does not suffer from this. It also uses the fragment approach that we use at Eclipse when repackaging the SLF4J and Logback bundles for Orbit. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 308] New: ErrorHandler should be an "interface", not a "class" - causes IncompatibleClassChangeError
by bugzilla-daemon＠qos.ch 24 Oct '13

24 Oct '13

http://bugzilla.slf4j.org/show_bug.cgi?id=308 Priority: P5 Bug ID: 308 Assignee: slf4j-dev(a)qos.ch Summary: ErrorHandler should be an "interface", not a "class" - causes IncompatibleClassChangeError Severity: enhancement Classification: Unclassified OS: Windows NT Reporter: brett.vasconcellos(a)bidstrading.com Hardware: PC Status: NEW Version: unspecified Component: log4j-over-slf4j Product: SLF4J If log4j-over-slf4j is used with code that has a class that "implement ErrorHandler", the class cannot be loaded and results in an IncompatibleClassChangeError Changing the "class" keyword to "interface" in ErrorHandler.java fixes the problem. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 173] New: slf4j android: Android throws an IllegalArgumentException when Log Tag length exceeds 23 characters
by bugzilla-daemon＠pixie.qos.ch 11 Sep '13

11 Sep '13

http://bugzilla.slf4j.org/show_bug.cgi?id=173 Summary: slf4j android: Android throws an IllegalArgumentException when Log Tag length exceeds 23 characters Product: SLF4J Version: 1.5.x Platform: Other OS/Version: other Status: NEW Severity: blocker Priority: P1 Component: Implementations AssignedTo: slf4j-dev(a)qos.ch ReportedBy: lorecarra(a)gmail.com I don't know if the 23-characters long tag limitation has been removed in later releases, but, unfortunately, Android 1.1 has it. I think the tag length should be checked and the tag eventually trimmed in order to avoid incurring in this exception without having to change the application logging code. The check is performed into the native method android.util.Log.isLoggable() To reproduce the problem in Android 1.1: String ALLOWED_TAG = "abcdefghijklmnopqrstuvw"; String TOO_LONG_TAG = "abcdefghijklmnopqrstuvwxyz"; Log.i(ALLOWED_TAG, "blabla"); Log.i(TOO_LONG_TAG, "blabla"); -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

2 19

[Bug 289] New: Add a NOOP method org.apache.log4j.Logger.setLevel() to enhance the bridging of Log4J over SLF4J
by bugzilla-daemon＠qos.ch 04 Sep '13

04 Sep '13

http://bugzilla.slf4j.org/show_bug.cgi?id=289 Summary: Add a NOOP method org.apache.log4j.Logger.setLevel() to enhance the bridging of Log4J over SLF4J Product: SLF4J Version: unspecified Platform: PC OS/Version: Mac OS X 10.3 Status: NEW Severity: enhancement Priority: P1 Component: log4j-over-slf4j AssignedTo: slf4j-dev(a)qos.ch ReportedBy: mspetrovic(a)gmail.com As a user of SLF4J who wants to bridge Log4J, I would like a org.apache.log4j.Logger.setLevel() method that is a NOOP implementation. Currently, this method does not exist on the org.apache.log4j.Logger class, and this causes a runtime exception to be thrown when 3rd party applications call legacy the method Logger.setLevel(Level lvl). Thanks. -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 4