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

From a56190cc108317d133af9fa00a0e7ed0ad0ae60e Mon Sep 17 00:00:00 2001
From: Minecrell <minecrell@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 bb32cb749d..a319cfe3b8 100644
--- a/pom.xml
+++ b/pom.xml
@@ -90,6 +90,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.18.0
Update B/CB/S 2018-07-23 10:39:55 +02:00			`From a56190cc108317d133af9fa00a0e7ed0ad0ae60e Mon Sep 17 00:00:00 2001`
[CI-SKIP] Add Minecrell to MIT list (#1035) Change email address for some older patches to make it clear that they are MIT licensed too. 2018-03-08 16:08:21 +01:00			`From: Minecrell <minecrell@minecrell.net>`
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			`Date: Thu, 21 Sep 2017 16:33:35 +0200`
			`Subject: [PATCH] Include Log4J2 SLF4J implementation`


			`diff --git a/pom.xml b/pom.xml`
Update B/CB/S 2018-07-23 10:39:55 +02:00			`index bb32cb749d..a319cfe3b8 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`
Update Paper to 1.13 proper - THIS IS STILL HIGHLY UNSTABLE DO NOT RUN ON PRODUCTION SERVERS!!! Use Backups!! 2018-07-22 07:27:46 +02:00			`@@ -90,6 +90,12 @@`
Fix NPE when getting location from players EnderChest (fixes #1041) 2018-03-10 14:07:40 +01:00			`</dependency>`

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			`<!-- Paper - Add additional Log4J dependencies -->`
Fix NPE when getting location from players EnderChest (fixes #1041) 2018-03-10 14:07:40 +01:00			`+ <dependency>`
			`+ <groupId>org.apache.logging.log4j</groupId>`
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			`+ <artifactId>log4j-slf4j-impl</artifactId>`
			`+ <version>2.8.1</version>`
			`+ <scope>runtime</scope>`
			`+ </dependency>`
Fix NPE when getting location from players EnderChest (fixes #1041) 2018-03-10 14:07:40 +01:00			`<dependency>`
			`<groupId>org.apache.logging.log4j</groupId>`
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			`<artifactId>log4j-iostreams</artifactId>`
			`--`
Fix issues with getBlockState(false) not loading Tile Entity data This only impacted people who used our useSnapshots new API in a plugin, which obviously was no one as the data result was completely broken. Merged the NPE check patch into mine since it has to handle it too. 2018-06-30 07:40:52 +02:00			`2.18.0`
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