Remove package scanning in log4j2 configuration

ModLauncher already includes the annotation processor that now writes the plugin metadata, making the deprecated packages attribute obsolete. This fixes warnings we get on startup: WARN StatusConsoleListener The use of package scanning to locate plugins is deprecated and will be removed in a future release
McModLauncher · Jul 4, 2024 · 9e7ce64 · 9e7ce64
1 parent 0f24dec
commit 9e7ce64
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/src/main/resources/log4j2.xml b/src/main/resources/log4j2.xml
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<Configuration status="warn" packages="cpw.mods.modlauncher.log">
+<Configuration status="warn">
     <filters>
         <MarkerFilter marker="NETWORK_PACKETS" onMatch="DENY" onMismatch="NEUTRAL"/>
         <MarkerFilter marker="CLASSLOADING" onMatch="DENY" onMismatch="NEUTRAL"/>

diff --git a/src/test/resources/log4j2.xml b/src/test/resources/log4j2.xml
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<Configuration status="warn" packages="cpw.mods.modlauncher.log">
+<Configuration status="warn">
     <filters>
         <MarkerFilter marker="NETWORK_PACKETS" onMatch="DENY" onMismatch="NEUTRAL"/>
         <MarkerFilter marker="CLASSLOADING" onMatch="DENY" onMismatch="NEUTRAL"/>