core
/
testserver
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
testserver/Spigot-Server-Patches/0236-Include-Log4J2-SLF4J-i...

27 lines
777 B
Diff
Raw Normal View History

Stop explicitly blocking Vanilla Method Profiler At the time this was re-added, there was concern around how the JIT would handle the system property that enabled it. This shouldn't be a problem, and as such we no longer need to block access to it. The Vanilla Method Profiler will not provide much to most users however there is no harm in providing it as an option. For most users, the recommended and supported method for determining performance issues with Paper will continue to be Timings.
2018-03-31 18:51:21 +00:00
From b810abd1c308634b722548b03cd532dba405ead6 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 15:08:21 +00: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 14:34:36 +00:00
Date: Thu, 21 Sep 2017 16:33:35 +0200
Subject: [PATCH] Include Log4J2 SLF4J implementation
diff --git a/pom.xml b/pom.xml
Stop explicitly blocking Vanilla Method Profiler At the time this was re-added, there was concern around how the JIT would handle the system property that enabled it. This shouldn't be a problem, and as such we no longer need to block access to it. The Vanilla Method Profiler will not provide much to most users however there is no harm in providing it as an option. For most users, the recommended and supported method for determining performance issues with Paper will continue to be Timings.
2018-03-31 18:51:21 +00:00
index 28976dae..ffa9f5a9 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 14:34:36 +00:00
--- a/pom.xml
+++ b/pom.xml
Fix NPE when getting location from players EnderChest (fixes #1041)
2018-03-10 13:07:40 +00:00
@@ -98,6 +98,12 @@
</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 14:34:36 +00:00
<!-- Paper - Add additional Log4J dependencies -->
Fix NPE when getting location from players EnderChest (fixes #1041)
2018-03-10 13:07:40 +00: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 14:34:36 +00: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 13:07:40 +00: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 14:34:36 +00:00
<artifactId>log4j-iostreams</artifactId>
--
Stop explicitly blocking Vanilla Method Profiler At the time this was re-added, there was concern around how the JIT would handle the system property that enabled it. This shouldn't be a problem, and as such we no longer need to block access to it. The Vanilla Method Profiler will not provide much to most users however there is no harm in providing it as an option. For most users, the recommended and supported method for determining performance issues with Paper will continue to be Timings.
2018-03-31 18:51:21 +00:00
2.14.3
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 14:34:36 +00:00