- slf4j-dev - mailman3.qos.ch

[JIRA] (SLF4J-426) Fix class name: SubstitureServiceProvider
by QOS.CH (JIRA) 30 Jan '18

30 Jan '18

[ https://jira.qos.ch/browse/SLF4J-426?page=com.atlassian.jira.plugin.system.… ] Ceki Gülcü resolved SLF4J-426. ------------------------------ Resolution: Fixed Fixed in [commit 805df| https://github.com/qos-ch/slf4j/commit/805df52bdcb86] > Fix class name: SubstitureServiceProvider > ----------------------------------------- > > Key: SLF4J-426 > URL: https://jira.qos.ch/browse/SLF4J-426 > Project: SLF4J > Issue Type: Bug > Components: Core API > Environment: __ > Reporter: PJ Fanning > Assignee: Ceki Gülcü > Fix For: 1.8.0-beta1 > > > Should be *SubstituteServiceProvider* > [https://github.com/qos-ch/slf4j/blob/master/slf4j-api/src/main/java/org/slf…] -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[qos-ch/slf4j] 805df5: fix SLF4J-426
by Ceki Gulcu 30 Jan '18

30 Jan '18

Branch: refs/heads/master Home: https://github.com/qos-ch/slf4j Commit: 805df52bdcb86718b01b3e9e20c7db639bb57a18 https://github.com/qos-ch/slf4j/commit/805df52bdcb86718b01b3e9e20c7db639bb5… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2018-01-30 (Tue, 30 Jan 2018) Changed paths: M slf4j-api/src/main/java/org/slf4j/LoggerFactory.java R slf4j-api/src/main/java/org/slf4j/helpers/SubstitureServiceProvider.java A slf4j-api/src/main/java/org/slf4j/helpers/SubstituteServiceProvider.java Log Message: ----------- fix SLF4J-426 Commit: dfe42a4ff34157497d0a2f7e59c535b825126cce https://github.com/qos-ch/slf4j/commit/dfe42a4ff34157497d0a2f7e59c535b82512… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2018-01-30 (Tue, 30 Jan 2018) Changed paths: M integration/pom.xml M jcl-over-slf4j/pom.xml M jul-to-slf4j/pom.xml M log4j-over-slf4j/pom.xml M osgi-over-slf4j/pom.xml M pom.xml M slf4j-api/pom.xml M slf4j-ext/pom.xml M slf4j-jdk14/pom.xml M slf4j-log4j12/pom.xml M slf4j-migrator/pom.xml M slf4j-nop/pom.xml M slf4j-simple/pom.xml M slf4j-site/pom.xml M slf4j-site/src/site/pages/news.html Log Message: ----------- prepare release 1.8.0-beta1 Compare: https://github.com/qos-ch/slf4j/compare/f8a590ea676c...dfe42a4ff341

1 0

[qos-ch/slf4j] 2ed256: Set Travis to run on Trusty and oraclejdk9.
by Ceki Gulcu 30 Jan '18

30 Jan '18

Branch: refs/heads/master Home: https://github.com/qos-ch/slf4j Commit: 2ed2565fe474a691171956c4572beef734d1180b https://github.com/qos-ch/slf4j/commit/2ed2565fe474a691171956c4572beef734d1… Author: Brett Randall <javabrett(a)gmail.com> Date: 2017-11-11 (Sat, 11 Nov 2017) Changed paths: M .travis.yml Log Message: ----------- Set Travis to run on Trusty and oraclejdk9. Commit: f13c8c20c26f268463879b2c4ffb408bca815f2c https://github.com/qos-ch/slf4j/commit/f13c8c20c26f268463879b2c4ffb408bca81… Author: Brett Randall <javabrett(a)gmail.com> Date: 2017-11-11 (Sat, 11 Nov 2017) Changed paths: M pom.xml Log Message: ----------- Added a profile for Travis executions and disabled maven-toolchains-plugin on Travis. Note that Travis will not support maven-toolchains-plugin, see https://github.com/travis-ci/travis-ci/issues/2727 . Commit: a8aa7832b7cb8091bc638d12a4fc1abfaaf44d8e https://github.com/qos-ch/slf4j/commit/a8aa7832b7cb8091bc638d12a4fc1abfaaf4… Author: Brett Randall <javabrett(a)gmail.com> Date: 2017-11-11 (Sat, 11 Nov 2017) Changed paths: M pom.xml Log Message: ----------- Added JDK9 to toolchains. Commit: b0fba1b48bb7e893905b9bb302f73dc72e8ef6b0 https://github.com/qos-ch/slf4j/commit/b0fba1b48bb7e893905b9bb302f73dc72e8e… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2018-01-30 (Tue, 30 Jan 2018) Changed paths: M .travis.yml M pom.xml Log Message: ----------- Merge branch 'travis' of git://github.com/javabrett/slf4j into javabrett-travis Commit: 2de3bc7edd446e5859ce748941d322651e756fc5 https://github.com/qos-ch/slf4j/commit/2de3bc7edd446e5859ce748941d322651e75… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2018-01-30 (Tue, 30 Jan 2018) Changed paths: M pom.xml Log Message: ----------- inverse Java 1.6/Java 9 jdk element in toolchains. This allows javadoc to be built Commit: f8a590ea676cecd814bcb577e413ff2e39f8142f https://github.com/qos-ch/slf4j/commit/f8a590ea676cecd814bcb577e413ff2e39f8… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2018-01-30 (Tue, 30 Jan 2018) Changed paths: M .travis.yml M pom.xml Log Message: ----------- Merge branch 'javabrett-travis' Compare: https://github.com/qos-ch/slf4j/compare/cda79c4eca3c...f8a590ea676c

1 0

[qos-ch/slf4j] cda79c: make createdPostInitialization variable final publ...
by Ceki Gulcu 30 Jan '18

30 Jan '18

Branch: refs/heads/master Home: https://github.com/qos-ch/slf4j Commit: cda79c4eca3c96637f94438ff51fcde164e67d24 https://github.com/qos-ch/slf4j/commit/cda79c4eca3c96637f94438ff51fcde164e6… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2018-01-30 (Tue, 30 Jan 2018) Changed paths: M slf4j-api/src/main/java/org/slf4j/helpers/SubstituteLogger.java Log Message: ----------- make createdPostInitialization variable final public

1 0

[JIRA] (SLF4J-427) Fix Travis build, toolchains, JDK9
by QOS.CH (JIRA) 30 Jan '18

30 Jan '18

Brett Randall created SLF4J-427: ----------------------------------- Summary: Fix Travis build, toolchains, JDK9 Key: SLF4J-427 URL: https://jira.qos.ch/browse/SLF4J-427 Project: SLF4J Issue Type: Task Components: Unspecified Affects Versions: 1.8.0-beta0 Environment: Travis build is for {{master}} currently errors-out due to problems with toolchain: {noformat} [INFO] Required toolchain: jdk [ version='1.6' ] [ERROR] No toolchain found for type jdk [ERROR] Cannot find matching toolchain definitions for the following toolchain types: jdk [ version='1.6' ] [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] [INFO] SLF4J .............................................. FAILURE [ 3.279 s] [INFO] SLF4J API Module ................................... SKIPPED{noformat} The build also requires JDK9 to complete in Travis. A matrix build is probably indicated, but let's get it building OK first. This is fixed by [https://github.com/qos-ch/slf4j/pull/187] . Last failed {{master}} Travis: [https://travis-ci.org/qos-ch/slf4j/builds/317439667 S|https://travis-ci.org/qos-ch/slf4j/builds/317439667]uccess from PR: [https://travis-ci.org/qos-ch/slf4j/builds/300534125] Please review and consider merging. Reporter: Brett Randall Assignee: SLF4J developers list -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (SLF4J-426) Fix class name: SubstitureServiceProvider
by QOS.CH (JIRA) 26 Jan '18

26 Jan '18

PJ Fanning created SLF4J-426: -------------------------------- Summary: Fix class name: SubstitureServiceProvider Key: SLF4J-426 URL: https://jira.qos.ch/browse/SLF4J-426 Project: SLF4J Issue Type: Bug Components: Core API Environment: Should be *SubstituteServiceProvider* [https://github.com/qos-ch/slf4j/blob/master/slf4j-api/src/main/java/org/slf…] Reporter: PJ Fanning Assignee: SLF4J developers list -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

JDK 10 Early Access b40 & JDK 8u172 Early Access b02 are available on jdk.java.net
by Rory O'Donnell 22 Jan '18

22 Jan '18

Hi Ceki, Happy New Year! *OpenJDK builds - *JDK 10 Early Access build 40 is available at http://jdk.java.net/10/ * These early-access, open-source builds are provided under the GNU General Public License, version 2, with the Classpath Exception <http://openjdk.java.net/legal/gplv2+ce.html>. * Summary of changes :- https://download.java.net/java/jdk10/archive/40/jdk-10+40.html *JDK 10 will enter Rampdown Phase Two on Thursday the 18th of January, 2018. * * More details , see Mark Reinhold's email to jdk-dev mailing list [1] * The Rampdown Phase Two process will be similar to that of JDK 9 [2]. * JDK 10 Schedule, Status & Features are available [3] *JDK **8u172 Early-Access build 03*is available at :- http://jdk.java.net/8/ * Summary of Changes here :- https://download.java.net/java/jdk8u172/changes/jdk8u172-b02.html <http://openjdk.java.net/projects/jdk8u/releases/8u162.html> Regards, Rory [1] http://mail.openjdk.java.net/pipermail/jdk-dev/2018-January/000416.html [2] http://openjdk.java.net/projects/jdk/10/rdp-2 [3] http://openjdk.java.net/projects/jdk/10/ -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA, Dublin,Ireland

1 0

[JIRA] (SLF4J-371) Support the lambda expression in the Logger
by QOS.CH (JIRA) 16 Jan '18

16 Jan '18

[ https://jira.qos.ch/browse/SLF4J-371?page=com.atlassian.jira.plugin.system.… ] Joerg commented on SLF4J-371: ----------------------------- Just came across this issue as Sonar complained about us not using a lambda. Is the invokedynamic call really a performance issue (couldn't find anything in that direction)? Especially for constant lambda expressions that are possibly inlined anyway? And even if there is a small performance penalty for the constant lambdas, wouldn't the lambda saving the "heavy" evaluation outweigh that? I propose to put a warning in the JavaDoc and let the user decide if it is neccessary and he is willing to pay the possible performance penalty. The effort of using lambdas everywhere is higher than simply providing objects to the log statements, so the amount of people using lambdas by accident should be non existent. > Support the lambda expression in the Logger > ------------------------------------------- > > Key: SLF4J-371 > URL: https://jira.qos.ch/browse/SLF4J-371 > Project: SLF4J > Issue Type: Improvement > Components: Core API > Affects Versions: 1.7.22 > Reporter: MiNG > Assignee: SLF4J developers list > > In some cases, we don't want to calculate the expression for logging eagerly cause the performance reason. Then, we would write the code like the following: > {code:java} > if (LOGGER.isWarnEnabled()) > { > LOGGER.warn("some message: {}", Json.serialize(obj)); > }{code} > Before JDK8, there is no way to encapsulate the above code, because the expression is always calculated before passed as an argument. So, many "if"s appear in the code and smell badly. > Now, the lambda expression is supported by JDK8, the above could be simplified like following: > {code:java} > LOGGER.warn(formatter -> formatter.format("some message: {}", Json.serialize(obj)));{code} > With the default method definition in the org.slf4j.Logger: > {code:java} > public interface Logger > { > default void warn(Function<MessageFormatter, String> messageSupplier) > { > if (this.isWarnEnabled()) > { > /* Calculate the expression only if the WARN level logging is enabled. */ > this.warn(messageSupplier.apply(this.getFormatter())); > } > } > }{code} -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

Apache logging log4j over slf4j
by Damien 10 Jan '18

10 Jan '18

Hi :), I am using a lib that uses log4j 2 (apache.logging.log4j.*). My build script (graddle) has easily replaced log4j 1 libs with log4j-over-slf4j, but does not handle log4j 2. Is there a version for log4j 2 ? Or is someone working on it ? Thanks :) Damien

2 6

[JIRA] (SLF4J-124) Add ability to log at a dynamic level
by QOS.CH (JIRA) 06 Jan '18

06 Jan '18

[ https://jira.qos.ch/browse/SLF4J-124?page=com.atlassian.jira.plugin.system.… ] Joel Handwell commented on SLF4J-124: ------------------------------------- Came from Stackoverflow and created JIRA account just for voting this. Hope this issue to be reviewed. > Add ability to log at a dynamic level > ------------------------------------- > > Key: SLF4J-124 > URL: https://jira.qos.ch/browse/SLF4J-124 > Project: SLF4J > Issue Type: Sub-task > Components: Core API > Affects Versions: 1.5.x > Environment: Operating System: All > Platform: All > URL: http://stackoverflow.com/questions/2621701/setting-log-level-of-message-at-… > Reporter: Robert Elliot > Assignee: SLF4J developers list > Attachments: Util.java.patch > > > It is occasionally useful to have a log method that takes a level as a parameter. The necessary methods can be added to the Util class without any compatibility issues as far as I can see - see attached patch. -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0