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

Jigsaw modularized version of SLF4J
by Ceki Gulcu 30 Mar '17

30 Mar '17

Hi all, You can find a Jigsaw modularized version of SLF4J at https://github.com/qos-ch/slf4j/tree/1_8_0-SNAPSHOT Unfortunately, due to javadoc issues, I was unable to deploy jar files to Maven Central. If interested in testing this Jigsaw modularized version, you need to compile from source. You also need to configure toolchains for JDK 9 and 6. There is some documentation on tools chains: https://maven.apache.org/guides/mini/guide-using-toolchains.html For good measure, here is my toolschains.xml file: <toolchains> <toolchain> <type>jdk</type> <provides> <version>1.6</version> </provides> <configuration> <jdkHome>c:/java/jdk1.7.0_80</jdkHome> </configuration> </toolchain> <toolchain> <type>jdk</type> <provides> <version>9</version> </provides> <configuration> <jdkHome>C:/java/jdk-9EA162/</jdkHome> </configuration> </toolchain> </toolchains> You would need to adapt it with the path to your JDK installations. Note that declared version 1.6 points to JDK 1.7. The slf4j/pom.xml requests JDK 6 by default. Comments welcome, -- Ceki

1 0

[JIRA] (SLF4J-365) CLONE - Provide a BOM of all slf4j artifacts
by QOS.CH (JIRA) 27 Mar '17

27 Mar '17

[ https://jira.qos.ch/browse/SLF4J-365?page=com.atlassian.jira.plugin.system.… ] Michael commented on SLF4J-365: ------------------------------- Please start another try with a BOM. Here is my version I'm using: {code:java} <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd"> <modelVersion>4.0.0</modelVersion> <groupId>org.slf4j</groupId> <artifactId>slf4j-bom</artifactId> <version>1.7.25</version> <packaging>pom</packaging> <url>http://www.slf4j.org</url> <name>SLF4J BOM</name> <licenses> <license> <name>MIT License</name> <url>http://www.opensource.org/licenses/mit-license.php</url> <distribution>repo</distribution> </license> </licenses> <dependencyManagement> <dependencies> <dependency> <groupId>org.slf4j</groupId> <artifactId>jcl-over-slf4j</artifactId> <version>${project.version}</version> </dependency> <dependency> <groupId>org.slf4j</groupId> <artifactId>jul-to-slf4j</artifactId> <version>${project.version}</version> </dependency> <dependency> <groupId>org.slf4j</groupId> <artifactId>log4j-over-slf4j</artifactId> <version>${project.version}</version> </dependency> <dependency> <groupId>org.slf4j</groupId> <artifactId>osgi-over-slf4j</artifactId> <version>${project.version}</version> </dependency> <dependency> <groupId>org.slf4j</groupId> <artifactId>slf4j-api</artifactId> <version>${project.version}</version> </dependency> <dependency> <groupId>org.slf4j</groupId> <artifactId>slf4j-jcl</artifactId> <version>${project.version}</version> </dependency> <dependency> <groupId>org.slf4j</groupId> <artifactId>slf4j-jdk14</artifactId> <version>${slf4j.version}</version> </dependency> <dependency> <groupId>org.slf4j</groupId> <artifactId>slf4j-log4j12</artifactId> <version>${project.version}</version> </dependency> <dependency> <groupId>org.slf4j</groupId> <artifactId>slf4j-simple</artifactId> <version>${project.version}</version> </dependency> <dependency> <groupId>org.slf4j</groupId> <artifactId>slf4j-nop</artifactId> <version>${project.version}</version> </dependency> <dependency> <groupId>org.slf4j</groupId> <artifactId>slf4j-ext</artifactId> <version>${project.version}</version> </dependency> </dependencies> </dependencyManagement> </project> {code} Kind regards, Michael > CLONE - Provide a BOM of all slf4j artifacts > -------------------------------------------- > > Key: SLF4J-365 > URL: https://jira.qos.ch/browse/SLF4J-365 > Project: SLF4J > Issue Type: New Feature > Reporter: Ceki Gülcü > Assignee: Ceki Gülcü > Fix For: 1.7.22 > > > We have an enterprise parent POM that defines versions of maven artifacts for all products that are built in our enterprise. > We want to define the version of all slf4j artifacts in that parent pom. Idealy we would just import a BOM (https://maven.apache.org/guides/introduction/introduction-to-dependency-mec…) > Instead of importing your BOM we now list all slf4j modules in our parent POM. Which means we have to check for new/changed modules with every version. > One example of a great BOM is [the log4j BOM|http://central.maven.org/maven2/org/apache/logging/log4j/log4j-bom/2.5/…] > Please provide a BOM just like Log4j2 does, so that we can import it in our enterprise parent pom. -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (SLF4J-401) Upgrade SLF4J binding mechanism to use java.util.ServiceLoader
by QOS.CH (JIRA) 25 Mar '17

25 Mar '17

[ https://jira.qos.ch/browse/SLF4J-401?page=com.atlassian.jira.plugin.system.… ] Ceki Gülcü commented on SLF4J-401: ---------------------------------- The details are still a bit murky but it seems to work now. > Upgrade SLF4J binding mechanism to use java.util.ServiceLoader > -------------------------------------------------------------- > > Key: SLF4J-401 > URL: https://jira.qos.ch/browse/SLF4J-401 > Project: SLF4J > Issue Type: Sub-task > Components: Core API > Reporter: Ceki Gülcü > Assignee: Ceki Gülcü > Priority: Blocker > Labels: binding > Fix For: 1.8.0 > > > The {{org.slf4j.impl.StaticXYZBinder}} approach has been surprisingly successful for such a crude mechanism. However, with the advent of Java 9/jigsaw/modularisation we need a more standard approach. {{java.util.ServiceLoader}} introduced in Java 6 seems to fit the bill. -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (SLF4J-402) Jigsaw module declerations
by QOS.CH (JIRA) 25 Mar '17

25 Mar '17

[ https://jira.qos.ch/browse/SLF4J-402?page=com.atlassian.jira.plugin.system.… ] Ceki Gülcü resolved SLF4J-402. ------------------------------ Resolution: Fixed Fix Version/s: 1.8.0 > Jigsaw module declerations > -------------------------- > > Key: SLF4J-402 > URL: https://jira.qos.ch/browse/SLF4J-402 > Project: SLF4J > Issue Type: Sub-task > Reporter: Ceki Gülcü > Assignee: SLF4J developers list > Fix For: 1.8.0 > > -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (SLF4J-401) Upgrade SLF4J binding mechanism to use java.util.ServiceLoader
by QOS.CH (JIRA) 25 Mar '17

25 Mar '17

[ https://jira.qos.ch/browse/SLF4J-401?page=com.atlassian.jira.plugin.system.… ] Ceki Gülcü resolved SLF4J-401. ------------------------------ Resolution: Fixed > Upgrade SLF4J binding mechanism to use java.util.ServiceLoader > -------------------------------------------------------------- > > Key: SLF4J-401 > URL: https://jira.qos.ch/browse/SLF4J-401 > Project: SLF4J > Issue Type: Sub-task > Components: Core API > Reporter: Ceki Gülcü > Assignee: Ceki Gülcü > Priority: Blocker > Labels: binding > Fix For: 1.8.0 > > > The {{org.slf4j.impl.StaticXYZBinder}} approach has been surprisingly successful for such a crude mechanism. However, with the advent of Java 9/jigsaw/modularisation we need a more standard approach. {{java.util.ServiceLoader}} introduced in Java 6 seems to fit the bill. -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[qos-ch/slf4j] 7a1d11: (OSGi-related) commented out Import-Package: org.s...
by Ceki Gulcu 25 Mar '17

25 Mar '17

Branch: refs/heads/1_8_0-SNAPSHOT Home: https://github.com/qos-ch/slf4j Commit: 7a1d11ef60fe38f158c967f5630a33863ae2269c https://github.com/qos-ch/slf4j/commit/7a1d11ef60fe38f158c967f5630a33863ae2… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2017-03-25 (Sat, 25 Mar 2017) Changed paths: M slf4j-api/src/main/resources/META-INF/MANIFEST.MF Log Message: ----------- (OSGi-related) commented out Import-Package: org.slf4j.impl in slf4j-api MANIFEST.MF file

1 0

[qos-ch/slf4j] 898104: deleteing log4j-over-slf4j/src/test/java/module-...
by Ceki Gulcu 25 Mar '17

25 Mar '17

Branch: refs/heads/1_8_0-SNAPSHOT Home: https://github.com/qos-ch/slf4j Commit: 89810489a18e323680c1bc3ffd5da2f267d46847 https://github.com/qos-ch/slf4j/commit/89810489a18e323680c1bc3ffd5da2f267d4… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2017-03-25 (Sat, 25 Mar 2017) Changed paths: R log4j-over-slf4j/src/test/java/module-info.java Log Message: ----------- deleteing log4j-over-slf4j/src/test/java/module-info.java

1 0

[qos-ch/slf4j] 129cf9: J2SE 1.5 is required
by Ceki Gulcu 25 Mar '17

25 Mar '17

Branch: refs/heads/1_8_0-SNAPSHOT Home: https://github.com/qos-ch/slf4j Commit: 129cf98bbdc1b901af73c690ff13d792ca4711d0 https://github.com/qos-ch/slf4j/commit/129cf98bbdc1b901af73c690ff13d792ca47… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2017-03-25 (Sat, 25 Mar 2017) Changed paths: M jcl-over-slf4j/src/main/resources/META-INF/MANIFEST.MF M jul-to-slf4j/src/main/resources/META-INF/MANIFEST.MF M log4j-over-slf4j/src/main/resources/META-INF/MANIFEST.MF M osgi-over-slf4j/src/main/resources/META-INF/MANIFEST.MF M slf4j-api/src/main/resources/META-INF/MANIFEST.MF M slf4j-ext/src/main/resources/META-INF/MANIFEST.MF M slf4j-jdk14/src/main/resources/META-INF/MANIFEST.MF M slf4j-log4j12/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: ----------- J2SE 1.5 is required

1 0

[qos-ch/slf4j] 054e72: following recommendations found at https://maven.a...
by Ceki Gulcu 25 Mar '17

25 Mar '17

Branch: refs/heads/1_8_0-SNAPSHOT Home: https://github.com/qos-ch/slf4j Commit: 054e720426103cb22d699a513b64bf6624ca020b https://github.com/qos-ch/slf4j/commit/054e720426103cb22d699a513b64bf6624ca… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2017-03-25 (Sat, 25 Mar 2017) Changed paths: M pom.xml Log Message: ----------- following recommendations found at https://maven.apache.org/plugins/maven-compiler-plugin/examples/module-info…

1 0

[JIRA] (SLF4J-401) Upgrade SLF4J binding mechanism to use java.util.ServiceLoader
by QOS.CH (JIRA) 25 Mar '17

25 Mar '17

[ https://jira.qos.ch/browse/SLF4J-401?page=com.atlassian.jira.plugin.system.… ] Patrick Reinhart commented on SLF4J-401: ---------------------------------------- The additional `module-info.class` in the root of the JAR want be a problem for an pre JDK 9 because it's not used there anyway. If you wanted to use JDK 9 specific stuff for let's say performance improvements, then a multi release JAR comes into play. There you can overwrite/add some classes using the JDK 9 specific stuff and put them into the same JAR. If that is not needed at the moment we do not need a multi release JAR at all. > Upgrade SLF4J binding mechanism to use java.util.ServiceLoader > -------------------------------------------------------------- > > Key: SLF4J-401 > URL: https://jira.qos.ch/browse/SLF4J-401 > Project: SLF4J > Issue Type: Sub-task > Components: Core API > Reporter: Ceki Gülcü > Assignee: Ceki Gülcü > Priority: Blocker > Labels: binding > Fix For: 1.8.0 > > > The {{org.slf4j.impl.StaticXYZBinder}} approach has been surprisingly successful for such a crude mechanism. However, with the advent of Java 9/jigsaw/modularisation we need a more standard approach. {{java.util.ServiceLoader}} introduced in Java 6 seems to fit the bill. -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0