- slf4j-dev - mailman3.qos.ch

[qos-ch/slf4j] bc0397: typo fix
by Ceki Gulcu 27 Apr '17

27 Apr '17

Branch: refs/heads/1_8_0-SNAPSHOT Home: https://github.com/qos-ch/slf4j Commit: bc03976da8bc0b4e83bae3dc7404336e03e22017 https://github.com/qos-ch/slf4j/commit/bc03976da8bc0b4e83bae3dc7404336e03e2… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2017-04-27 (Thu, 27 Apr 2017) Changed paths: M slf4j-site/src/site/pages/news.html Log Message: ----------- typo fix

1 0

[qos-ch/slf4j] 4772ff: start work on 1.8.0-alpha3-SNAPSHOT
by Ceki Gulcu 27 Apr '17

27 Apr '17

Branch: refs/heads/1_8_0-SNAPSHOT Home: https://github.com/qos-ch/slf4j Commit: 4772fff68123c337e1b39de4ab8789faa8c98f1b https://github.com/qos-ch/slf4j/commit/4772fff68123c337e1b39de4ab8789faa8c9… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2017-04-27 (Thu, 27 Apr 2017) 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 Log Message: ----------- start work on 1.8.0-alpha3-SNAPSHOT

1 0

[JIRA] (SLF4J-407) Jigsaw modules contain clashing package
by QOS.CH (JIRA) 26 Apr '17

26 Apr '17

[ https://jira.qos.ch/browse/SLF4J-407?page=com.atlassian.jira.plugin.system.… ] Ceki Gülcü reopened SLF4J-407: ------------------------------ Assignee: Ceki Gülcü (was: SLF4J developers list) > Jigsaw modules contain clashing package > --------------------------------------- > > Key: SLF4J-407 > URL: https://jira.qos.ch/browse/SLF4J-407 > Project: SLF4J > Issue Type: Bug > Components: Implementations > Affects Versions: 1.8.0-alpha1 > Reporter: Stephen Colebourne > Assignee: Ceki Gülcü > Fix For: 1.8.0-alpha2 > > > Looking at the slf4j-jdk14 and slf4j-nop artifacts, they both appear to contain the package `org.slf4j.impl`. Jigsaw will refuse to load two modules that contain the same package, so this will be a problem. > I know that SLF4J does not intend users to load both of these modules at the same time. But the current setup means that it will be the JPMS runtime that rejects it, meaning that there is no chance for SLF4J to output a helpful message (as I believe it does today). > The solution to this would appear to be to move the `org.slf4j.impl` package to `org.slf4j.jul.impl` and `org.slf4j.nop.impl`. As the impl package is not exported, this should not affect any user code (except code that would have been affected anyway). > I imagine this affects other slf4j artifacts. > I also note that [this module-info.java|https://github.com/qos-ch/slf4j/blob/1_8_0-SNAPSHOT/slf4j-…] exports the `org.slf4j.jul` package, which seems unnecessary (simple and nop do not export their package). > See [here|http://blog.joda.org/2017/04/java-se-9-jpms-module-naming.html] for more information on naming. -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (SLF4J-407) Jigsaw modules contain clashing package
by QOS.CH (JIRA) 26 Apr '17

26 Apr '17

[ https://jira.qos.ch/browse/SLF4J-407?page=com.atlassian.jira.plugin.system.… ] Ceki Gülcü commented on SLF4J-407: ---------------------------------- At present time, it seems that including org.slf4j.impl packages in order to cater for older versions of slf4j-api.jar in the class path seems worthwhile at the moment. By the way, I acknowledge your point about JPMS runtime rejecting multiple providers on the class path, leaving no opportunity to SLF4J to output a helpful message. I am somewhat conflicted about including org.slf4j.impl packages in slf4j providers and intend to revisit the issue in the near future. > Jigsaw modules contain clashing package > --------------------------------------- > > Key: SLF4J-407 > URL: https://jira.qos.ch/browse/SLF4J-407 > Project: SLF4J > Issue Type: Bug > Components: Implementations > Affects Versions: 1.8.0-alpha1 > Reporter: Stephen Colebourne > Assignee: SLF4J developers list > Fix For: 1.8.0-alpha2 > > > Looking at the slf4j-jdk14 and slf4j-nop artifacts, they both appear to contain the package `org.slf4j.impl`. Jigsaw will refuse to load two modules that contain the same package, so this will be a problem. > I know that SLF4J does not intend users to load both of these modules at the same time. But the current setup means that it will be the JPMS runtime that rejects it, meaning that there is no chance for SLF4J to output a helpful message (as I believe it does today). > The solution to this would appear to be to move the `org.slf4j.impl` package to `org.slf4j.jul.impl` and `org.slf4j.nop.impl`. As the impl package is not exported, this should not affect any user code (except code that would have been affected anyway). > I imagine this affects other slf4j artifacts. > I also note that [this module-info.java|https://github.com/qos-ch/slf4j/blob/1_8_0-SNAPSHOT/slf4j-…] exports the `org.slf4j.jul` package, which seems unnecessary (simple and nop do not export their package). > See [here|http://blog.joda.org/2017/04/java-se-9-jpms-module-naming.html] for more information on naming. -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[qos-ch/slf4j]
by ceki 25 Apr '17

25 Apr '17

Branch: refs/tags/v_1.8.0-alpha2 Home: https://github.com/qos-ch/slf4j

1 0

[JIRA] (SLF4J-407) Jigsaw modules contain clashing package
by QOS.CH (JIRA) 25 Apr '17

25 Apr '17

[ https://jira.qos.ch/browse/SLF4J-407?page=com.atlassian.jira.plugin.system.… ] Ceki Gülcü resolved SLF4J-407. ------------------------------ Resolution: Fixed > Jigsaw modules contain clashing package > --------------------------------------- > > Key: SLF4J-407 > URL: https://jira.qos.ch/browse/SLF4J-407 > Project: SLF4J > Issue Type: Bug > Components: Implementations > Affects Versions: 1.8.0-alpha1 > Reporter: Stephen Colebourne > Assignee: SLF4J developers list > Fix For: 1.8.0-alpha2 > > > Looking at the slf4j-jdk14 and slf4j-nop artifacts, they both appear to contain the package `org.slf4j.impl`. Jigsaw will refuse to load two modules that contain the same package, so this will be a problem. > I know that SLF4J does not intend users to load both of these modules at the same time. But the current setup means that it will be the JPMS runtime that rejects it, meaning that there is no chance for SLF4J to output a helpful message (as I believe it does today). > The solution to this would appear to be to move the `org.slf4j.impl` package to `org.slf4j.jul.impl` and `org.slf4j.nop.impl`. As the impl package is not exported, this should not affect any user code (except code that would have been affected anyway). > I imagine this affects other slf4j artifacts. > I also note that [this module-info.java|https://github.com/qos-ch/slf4j/blob/1_8_0-SNAPSHOT/slf4j-…] exports the `org.slf4j.jul` package, which seems unnecessary (simple and nop do not export their package). > See [here|http://blog.joda.org/2017/04/java-se-9-jpms-module-naming.html] for more information on naming. -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[qos-ch/slf4j] 70ec42: prepare release 1.8.0-alpha2
by Ceki Gulcu 25 Apr '17

25 Apr '17

Branch: refs/heads/1_8_0-SNAPSHOT Home: https://github.com/qos-ch/slf4j Commit: 70ec42263abf188950cd2a8f8eb4502c9c372ac1 https://github.com/qos-ch/slf4j/commit/70ec42263abf188950cd2a8f8eb4502c9c37… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2017-04-26 (Wed, 26 Apr 2017) 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/codes.html Log Message: ----------- prepare release 1.8.0-alpha2

1 0

[qos-ch/slf4j] 2ff447: doc improvements
by Ceki Gulcu 25 Apr '17

25 Apr '17

Branch: refs/heads/1_8_0-SNAPSHOT Home: https://github.com/qos-ch/slf4j Commit: 2ff447be268ab736dd64d908d4ec922292341c8e https://github.com/qos-ch/slf4j/commit/2ff447be268ab736dd64d908d4ec92229234… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2017-04-26 (Wed, 26 Apr 2017) Changed paths: M slf4j-site/src/site/pages/codes.html M slf4j-site/src/site/pages/faq.html M slf4j-site/src/site/pages/news.html Log Message: ----------- doc improvements

1 0

[JIRA] (SLF4J-407) Jigsaw modules contain clashing package
by QOS.CH (JIRA) 25 Apr '17

25 Apr '17

[ https://jira.qos.ch/browse/SLF4J-407?page=com.atlassian.jira.plugin.system.… ] Ceki Gülcü commented on SLF4J-407: ---------------------------------- The `org.slf4j.jul` package is no longer exported by slf4j-jdk14. See [commit 3823bd|https://github.com/qos-ch/slf4j/commit/3823bd18e8829e72bf4a63cca62eb] As for the `org.slf4j.impl` packages included in various slf4j artifacts, I am afraid these cannot be changed. The reasons are mentioned in this [faq entry|https://www.slf4j.org/faq.html#changesInVersion18] Please let me know if the reasons are clear. > Jigsaw modules contain clashing package > --------------------------------------- > > Key: SLF4J-407 > URL: https://jira.qos.ch/browse/SLF4J-407 > Project: SLF4J > Issue Type: Bug > Components: Implementations > Affects Versions: 1.8.0-alpha1 > Reporter: Stephen Colebourne > Assignee: SLF4J developers list > Fix For: 1.8.0-alpha2 > > > Looking at the slf4j-jdk14 and slf4j-nop artifacts, they both appear to contain the package `org.slf4j.impl`. Jigsaw will refuse to load two modules that contain the same package, so this will be a problem. > I know that SLF4J does not intend users to load both of these modules at the same time. But the current setup means that it will be the JPMS runtime that rejects it, meaning that there is no chance for SLF4J to output a helpful message (as I believe it does today). > The solution to this would appear to be to move the `org.slf4j.impl` package to `org.slf4j.jul.impl` and `org.slf4j.nop.impl`. As the impl package is not exported, this should not affect any user code (except code that would have been affected anyway). > I imagine this affects other slf4j artifacts. > I also note that [this module-info.java|https://github.com/qos-ch/slf4j/blob/1_8_0-SNAPSHOT/slf4j-…] exports the `org.slf4j.jul` package, which seems unnecessary (simple and nop do not export their package). > See [here|http://blog.joda.org/2017/04/java-se-9-jpms-module-naming.html] for more information on naming. -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[qos-ch/slf4j] 3823bd: no need to export 'org.slf4j.jul' package
by Ceki Gulcu 25 Apr '17

25 Apr '17

Branch: refs/heads/1_8_0-SNAPSHOT Home: https://github.com/qos-ch/slf4j Commit: 3823bd18e8829e72bf4a63cca62eb6c27e9132b6 https://github.com/qos-ch/slf4j/commit/3823bd18e8829e72bf4a63cca62eb6c27e91… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2017-04-25 (Tue, 25 Apr 2017) Changed paths: M slf4j-jdk14/src/main/java/module-info.java Log Message: ----------- no need to export 'org.slf4j.jul' package

1 0