Paper-Old/Spigot-Server-Patches/0239-Include-Log4J2-SLF4J-implementation.patch

From 3eed4ccb095324b5502a8c4872320f2161dc505e Mon Sep 17 00:00:00 2001
From: Minecrell <dev@minecrell.net>
Date: Thu, 21 Sep 2017 16:33:35 +0200
Subject: [PATCH] Include Log4J2 SLF4J implementation


diff --git a/pom.xml b/pom.xml
index dfb006aa0..07e780b6f 100644
--- a/pom.xml
+++ b/pom.xml
@@ -98,6 +98,12 @@
         </dependency>
 
         <!-- Paper - Add additional Log4J dependencies -->
+        <dependency>
+            <groupId>org.apache.logging.log4j</groupId>
+            <artifactId>log4j-slf4j-impl</artifactId>
+            <version>2.8.1</version>
+            <scope>runtime</scope>
+        </dependency>
         <dependency>
             <groupId>org.apache.logging.log4j</groupId>
             <artifactId>log4j-iostreams</artifactId>
-- 
2.14.2
Update CB/S 2017-10-07 10:57:38 +02:00			`From 3eed4ccb095324b5502a8c4872320f2161dc505e Mon Sep 17 00:00:00 2001`
Allow plugins to use SLF4J for logging SLF4J is a commonly used abstraction for various logging frameworks such as java.util.logging (JUL) or Log4j. Currently, plugins are required to do all their logging using the provided JUL logger. This is annoying for plugins that target multiple platforms or when using libraries that log messages using SLF4J. Expose SLF4J as optional logging API for plugins, so they can use it without having to shade it in the plugin and going through several layers of logging abstraction. 2017-09-21 16:34:36 +02:00			`From: Minecrell <dev@minecrell.net>`
			`Date: Thu, 21 Sep 2017 16:33:35 +0200`
			`Subject: [PATCH] Include Log4J2 SLF4J implementation`


			`diff --git a/pom.xml b/pom.xml`
Update CB/S 2017-10-07 10:57:38 +02:00			`index dfb006aa0..07e780b6f 100644`
Allow plugins to use SLF4J for logging SLF4J is a commonly used abstraction for various logging frameworks such as java.util.logging (JUL) or Log4j. Currently, plugins are required to do all their logging using the provided JUL logger. This is annoying for plugins that target multiple platforms or when using libraries that log messages using SLF4J. Expose SLF4J as optional logging API for plugins, so they can use it without having to shade it in the plugin and going through several layers of logging abstraction. 2017-09-21 16:34:36 +02:00			`--- a/pom.xml`
			`+++ b/pom.xml`
			`@@ -98,6 +98,12 @@`
			`</dependency>`

			`<!-- Paper - Add additional Log4J dependencies -->`
			`+ <dependency>`
			`+ <groupId>org.apache.logging.log4j</groupId>`
			`+ <artifactId>log4j-slf4j-impl</artifactId>`
			`+ <version>2.8.1</version>`
			`+ <scope>runtime</scope>`
			`+ </dependency>`
			`<dependency>`
			`<groupId>org.apache.logging.log4j</groupId>`
			`<artifactId>log4j-iostreams</artifactId>`
			`--`
Update CB/S 2017-10-07 10:57:38 +02:00			`2.14.2`
Allow plugins to use SLF4J for logging SLF4J is a commonly used abstraction for various logging frameworks such as java.util.logging (JUL) or Log4j. Currently, plugins are required to do all their logging using the provided JUL logger. This is annoying for plugins that target multiple platforms or when using libraries that log messages using SLF4J. Expose SLF4J as optional logging API for plugins, so they can use it without having to shade it in the plugin and going through several layers of logging abstraction. 2017-09-21 16:34:36 +02:00