August 2017 - slf4j-dev - mailman3.qos.ch

[JIRA] (SLF4J-314) slf4j not logging VERBOSE and DEBUG messages, no matter what is Logcat's loglevel
by QOS.CH (JIRA) 31 Aug '17

31 Aug '17

[ https://jira.qos.ch/browse/SLF4J-314?page=com.atlassian.jira.plugin.system.… ] Mike Mitterer commented on SLF4J-314: ------------------------------------- Guys, [~nitin_matrix] this is a bug! If I want debug output the slf4j should give me what I want. Androids TAG-based approach is crap. This is how I set my logger: private static Logger logger = LoggerFactory.getLogger(Connection.class); setprop fails because it tells me that my name for the full class is to long. [~vyzivus] is approach is much better! > slf4j not logging VERBOSE and DEBUG messages, no matter what is Logcat's loglevel > --------------------------------------------------------------------------------- > > Key: SLF4J-314 > URL: https://jira.qos.ch/browse/SLF4J-314 > Project: SLF4J > Issue Type: Bug > Components: slf4j-android > Affects Versions: 1.7.x > Environment: Operating System: All > Platform: Other > Reporter: Mark Zalavari > Assignee: SLF4J developers list > > It seems on android platform the isLoggable() method is always returns false for VERBOSE and DEBUG (no matter what is the actal loglevel is), so it should not be called before calling Log.d and Log.v > The only slf4j version I know of where the DEBUG & VERBOSE logs are working is 1.6.1-RC1 -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (SLF4J-418) Add JSR 305 to SLF4j
by QOS.CH (JIRA) 13 Aug '17

13 Aug '17

Erik Pragt created SLF4J-418: -------------------------------- Summary: Add JSR 305 to SLF4j Key: SLF4J-418 URL: https://jira.qos.ch/browse/SLF4J-418 Project: SLF4J Issue Type: Bug Components: Core API Affects Versions: 2.0 Reporter: Erik Pragt Assignee: SLF4J developers list A few years ago, attempts have been made to implement JSR 305 in SLF4j. This was rolled back due to a Scala compiler issue, which, 5 years later, still hasn't been fixed. In the meantime, other libraries, like Guava, most of Square's libraries ([https://medium.com/square-corner-blog/rolling-out-nullable-42dd823fbd89) the Spring framework, etc, have implemented JSR 305. JSR 305 is now supported by tools like Findbugs, and languages like Kotlin, and IDEs like Eclipse and IntelliJ make use of this meta information to detect bugs. I hope that by now, we can also add JSR 305 information into SLF4j. If the Scala issue is still an issue, it seems that this issue should either be fixed by Lightbend, or they will run into issues with other frameworks anyway. Anyhow, IMO, it seems the Scala compiler should not be a reason to withhold this change from happening. The main motivation is that it will make programming in Kotlin easier (right now, types from SLF4j are platform types, and the compiler has no information if this is a nullable or non-nullable type, making SLF4j harder to use), but, as a side effect, it will help IDEs and other tooling. -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

Passed: leusonmario/slf4j#1 (master - 3278345)
by Travis CI 10 Aug '17

10 Aug '17

Build Update for leusonmario/slf4j ------------------------------------- Build: #1 Status: Passed Duration: 2 minutes and 21 seconds Commit: 3278345 (master) Author: Luke Cwik Message: Merge remote-tracking branch 'upstream/master' Fix merge conflict in BasicMDCAdapter.java View the changeset: https://github.com/leusonmario/slf4j/compare/d9280190fb73...32783459528c View the full build log and details: https://travis-ci.org/leusonmario/slf4j/builds/263201243?utm_source=email&u… -- You can configure recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications

1 0

[JIRA] (SLF4J-417) ILoggerFactory Documentation Grammer
by QOS.CH (JIRA) 09 Aug '17

09 Aug '17

Ryan McCullagh created SLF4J-417: ------------------------------------ Summary: ILoggerFactory Documentation Grammer Key: SLF4J-417 URL: https://jira.qos.ch/browse/SLF4J-417 Project: SLF4J Issue Type: Improvement Components: Core API Affects Versions: 1.7.25 Reporter: Ryan McCullagh Assignee: SLF4J developers list Priority: Trivial -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

Ready for JDK 9 ?
by Rory O'Donnell 08 Aug '17

08 Aug '17

Hi Ceki, Thank you very much for all your testing of JDK 9 during its development! Such contributions have significantly helped shape and improve JDK 9. Now that we have reached the JDK 9 Final Release Candidate phase [1] , I would like to ask if your project can be considered to be 'ready for JDK 9', or if there are any remaining show stopper issues which you've encountered when testing with the JDK 9 release candidate. JDK 9 b181 is available at http://jdk.java.net/9/ If you have a public web page, mailing list post, or even a tweet announcing you project's readiness for JDK 9, I'd love to add the URL to the upcoming JDK 9 readiness page on the Quality Outreach wiki. Looking forward to hearing from you, Rory [1] http://openjdk.java.net/projects/jdk9/ -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA , Dublin, Ireland

1 0