From 971e345ea3bbb4f4ad6d36b52a2d400d024e60d3 Mon Sep 17 00:00:00 2001
From: Sekelenao <Sekelenao@protonmail.com>
Date: Wed, 19 Aug 2026 23:37:29 +0200
Subject: [PATCH] [build] Exclude module-info.class from shaded JARs to prevent
 JPMS conflicts

Exclude module-info.class and multi-release module-info.class files
from all shaded dependencies in root pom.xml. This prevents third-party
module descriptors (e.g. from commons-lang3) from leaking into shaded
fat-JARs and breaking JPMS modular consumption.

Fixes #4045
---
 pom.xml | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/pom.xml b/pom.xml
index ae0e5cf582..d0b1754aa1 100644
--- a/pom.xml
+++ b/pom.xml
@@ -886,6 +886,11 @@
                                 <exclude>log4j2.properties</exclude>
                                 <exclude>log4j-test.properties</exclude>
                                 <exclude>log4j2-test.properties</exclude>
+                                <!-- Do not copy module-info.class from shaded dependencies.
+                                     Otherwise, the shaded uber-JAR will inherit a third-party module descriptor (e.g. from commons-lang3)
+                                     which breaks JPMS modular consumption. -->
+                                <exclude>module-info.class</exclude>
+                                <exclude>META-INF/versions/**/module-info.class</exclude>
                                 <!-- Do not copy the signatures in the META-INF folder.
                                 Otherwise, this might cause SecurityExceptions when using the JAR. -->
                                 <exclude>META-INF/*.SF</exclude>