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

[JIRA] (SLF4J-420) Make a release with Automatic-Module-Name
by QOS.CH (JIRA) 06 Aug '19

06 Aug '19

[ https://jira.qos.ch/browse/SLF4J-420?page=com.atlassian.jira.plugin.system.… ] John Patrick commented on SLF4J-420: ------------------------------------ I don't really mine what the JPMS module name is, as for the past 3 years I've been having to use the file based module name so that was/is slf4j.api. But I would assume it's most logical name for the org.slf4j:slf4j-api artifact to be org.slf4j.api. I'm restricted from building and releasing code that is still considered alpha/beta/RC. So I can't use your 15 month old 1.8.x beta or the 6 month old 2.0.x alpha. I don't understand what the objection is to add the Automatic Module Name to the 1.7.x branch. If the maven artifacts are just minor or major version upgrades and it's using the same module name it means people can start using the correct module name and get the true JPMS benefits when 1.8.x and/or 2.0.x are finally released. Yes some project use/depend on old versions, I'm trying to get them upgraded too. I've got forks of some projects I'm trying to get merged using the correct module names but I don't want to merge module-info.java files which contain filename-based automodules detected as it just causes issues once the project actually start using a module name. For me log4j-over-slf4j was just more a comment as i noticed it, for testing and runtime I've not yet really cased about and just open as needed, trying to sort out the compile time first. Just to confirm, once I found slf4j I switched over everything I could. I really like what it is, everything i write is slf4j with a log4j backend (because of ease of both MDC and the programmatic based configuration file reloading option). Adding other Java 8 or newer features into slf4j I'm happy to wait until ready and full working as 1.7.x gives me everything i currently need apart form being able to do module builds. I'm aware you have issues as it doesn't produce a full module map but it's once less issue in the future and will be fixed once i get a java 11 version of slf4j. > Make a release with Automatic-Module-Name > ----------------------------------------- > > Key: SLF4J-420 > URL: https://jira.qos.ch/browse/SLF4J-420 > Project: SLF4J > Issue Type: Task > Reporter: Gael Lalire > Assignee: Ceki Gülcü > Priority: Trivial > Fix For: 1.7.27 > > > You can make a release with Automatic-Module-Name with 1.7 version so it can load logback and have the package name you choose in 1.8 beta. -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[qos-ch/slf4j] d50742: update 1, 7, 27 release information
by Ceki Gulcu 06 Aug '19

06 Aug '19

Branch: refs/heads/master Home: https://github.com/qos-ch/slf4j Commit: d5074263f87b1b8b824e51cfc6e72d25b01c1ccb https://github.com/qos-ch/slf4j/commit/d5074263f87b1b8b824e51cfc6e72d25b01c… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2019-08-06 (Tue, 06 Aug 2019) Changed paths: M pom.xml M slf4j-site/src/site/pages/news.html Log Message: ----------- update 1,7,27 release information

1 0

[qos-ch/slf4j]
by Ceki Gulcu 06 Aug '19

06 Aug '19

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

1 0

[qos-ch/slf4j] 4c6c57: fix javadoc issues
by Ceki Gulcu 06 Aug '19

06 Aug '19

Branch: refs/heads/1.7-maintenance Home: https://github.com/qos-ch/slf4j Commit: 4c6c574a7a742d07aee788ade66f2f9b8f0c6c34 https://github.com/qos-ch/slf4j/commit/4c6c574a7a742d07aee788ade66f2f9b8f0c… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2019-08-06 (Tue, 06 Aug 2019) Changed paths: M pom.xml Log Message: ----------- fix javadoc issues

1 0

[JIRA] (SLF4J-420) Make a release with Automatic-Module-Name
by QOS.CH (JIRA) 06 Aug '19

06 Aug '19

[ https://jira.qos.ch/browse/SLF4J-420?page=com.atlassian.jira.plugin.system.… ] Ceki Gülcü resolved SLF4J-420. ------------------------------ Resolution: Fixed > Make a release with Automatic-Module-Name > ----------------------------------------- > > Key: SLF4J-420 > URL: https://jira.qos.ch/browse/SLF4J-420 > Project: SLF4J > Issue Type: Task > Reporter: Gael Lalire > Assignee: Ceki Gülcü > Priority: Trivial > Fix For: 1.7.27 > > > You can make a release with Automatic-Module-Name with 1.7 version so it can load logback and have the package name you choose in 1.8 beta. -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (SLF4J-420) Make a release with Automatic-Module-Name
by QOS.CH (JIRA) 05 Aug '19

05 Aug '19

[ https://jira.qos.ch/browse/SLF4J-420?page=com.atlassian.jira.plugin.system.… ] Ceki Gülcü commented on SLF4J-420: ---------------------------------- {{\{quote}}} {{why is log4j-over-slf4j just "log4j", because if you have an old dependency for log4j and need to use file name based modules, then that module will be called "log4j", should it not be "org.slf4j.log4j?}} {{\{quote}}}{{}} Your question contains the answer? As you put it, i{{f you have an old dependency for log4j and need to use file name based modules, then that module will be called "log4j".}} {{\{quote}}}{{}} {{Also as these maven modules for 1.x appear to match 2.x, then whey can't these names be used for a 1.7.27 release so those downstream projects that have been waiting for nearly 2 years can upgrade easily without have to do a major upgrade release...}} {{\{quote}}}{{}} It's quite late here and I don't understand. Can you please give an example? > Make a release with Automatic-Module-Name > ----------------------------------------- > > Key: SLF4J-420 > URL: https://jira.qos.ch/browse/SLF4J-420 > Project: SLF4J > Issue Type: Task > Reporter: Gael Lalire > Assignee: Ceki Gülcü > Priority: Trivial > Fix For: 1.7.27 > > > You can make a release with Automatic-Module-Name with 1.7 version so it can load logback and have the package name you choose in 1.8 beta. -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[qos-ch/slf4j] 71291d: prepare release 1.7.27
by Ceki Gulcu 05 Aug '19

05 Aug '19

Branch: refs/heads/1.7-maintenance Home: https://github.com/qos-ch/slf4j Commit: 71291d97bab676addb1a832d43b7fe7ad6128822 https://github.com/qos-ch/slf4j/commit/71291d97bab676addb1a832d43b7fe7ad612… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2019-08-06 (Tue, 06 Aug 2019) 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-android/pom.xml M slf4j-api/pom.xml M slf4j-ext/pom.xml M slf4j-jcl/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: ----------- prepare release 1.7.27

1 0

[qos-ch/slf4j] bf50c4: fix SLF4J-420
by Ceki Gulcu 05 Aug '19

05 Aug '19

Branch: refs/heads/1.7-maintenance Home: https://github.com/qos-ch/slf4j Commit: bf50c49d10e37e4d0c82a2529c2f074237262db1 https://github.com/qos-ch/slf4j/commit/bf50c49d10e37e4d0c82a2529c2f07423726… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2019-08-06 (Tue, 06 Aug 2019) Changed paths: M jcl-over-slf4j/src/main/resources/META-INF/MANIFEST.MF M log4j-over-slf4j/src/main/resources/META-INF/MANIFEST.MF M slf4j-api/src/main/resources/META-INF/MANIFEST.MF M slf4j-jdk14/src/main/resources/META-INF/MANIFEST.MF M slf4j-nop/src/main/resources/META-INF/MANIFEST.MF M slf4j-simple/src/main/resources/META-INF/MANIFEST.MF Log Message: ----------- fix SLF4J-420

1 0

[JIRA] (SLF4J-420) Make a release with Automatic-Module-Name
by QOS.CH (JIRA) 05 Aug '19

05 Aug '19

[ https://jira.qos.ch/browse/SLF4J-420?page=com.atlassian.jira.plugin.system.… ] John Patrick commented on SLF4J-420: ------------------------------------ why is log4j-over-slf4j just "log4j", because if you have and old dependency for log4j and need to use file name based modules, then that module will be called "log4j", should it not be "org.slf4j.log4j? Also as these maven modules for 1.x appear to match 2.x, then whey can't these names be used for a 1.7.27 release so those downstream projects that have been waiting for nearly 2 years can upgrade easily without have to do a major upgrade release... > Make a release with Automatic-Module-Name > ----------------------------------------- > > Key: SLF4J-420 > URL: https://jira.qos.ch/browse/SLF4J-420 > Project: SLF4J > Issue Type: Task > Reporter: Gael Lalire > Assignee: Ceki Gülcü > Priority: Trivial > Fix For: 1.7.27 > > > You can make a release with Automatic-Module-Name with 1.7 version so it can load logback and have the package name you choose in 1.8 beta. -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (SLF4J-420) Make a release with Automatic-Module-Name
by QOS.CH (JIRA) 05 Aug '19

05 Aug '19

[ https://jira.qos.ch/browse/SLF4J-420?page=com.atlassian.jira.plugin.system.… ] Ceki Gülcü commented on SLF4J-420: ---------------------------------- Module names extracted from the master (2.0) branch: || maven module || JMPS module name || |slf4j-api |org.slf4j | |slf4j-jdk14|org.slf4j.jul | |slf4j-nop|org.slf4j.nop | |slf4j-simple| org.slf4j.simple | |jcl-over-slf4j| org.apache.commons.logging | |log4j-over-slf4j/|log4j| > Make a release with Automatic-Module-Name > ----------------------------------------- > > Key: SLF4J-420 > URL: https://jira.qos.ch/browse/SLF4J-420 > Project: SLF4J > Issue Type: Task > Reporter: Gael Lalire > Assignee: Ceki Gülcü > Priority: Trivial > Fix For: 1.7.27 > > > You can make a release with Automatic-Module-Name with 1.7 version so it can load logback and have the package name you choose in 1.8 beta. -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0