From 19e5e82e2a2df0c6a0775a0cd2320bfd9c5d0954 Mon Sep 17 00:00:00 2001 From: Leon van Zantvoort Date: Mon, 10 Aug 2026 21:11:59 +0200 Subject: [PATCH] chore: suppress module-not-found warnings for storm-core qualified exports The impl packages are exported to Storm's sibling modules only. Those siblings depend on storm-core, so none of them are observable while storm-core itself compiles and javac emits a "module not found" warning for every qualified-export target. Annotate the module declaration with @SuppressWarnings("module") to keep the build output clean; the exports resolve as intended once the siblings compile with storm-core on their module path. --- storm-core/src/main/java/module-info.java | 3 +++ 1 file changed, 3 insertions(+) diff --git a/storm-core/src/main/java/module-info.java b/storm-core/src/main/java/module-info.java index ea1b99139..f2d5fdcf2 100644 --- a/storm-core/src/main/java/module-info.java +++ b/storm-core/src/main/java/module-info.java @@ -1,3 +1,6 @@ +// The qualified exports below target sibling modules that depend on storm-core, so they are never +// observable while storm-core itself compiles; suppress the resulting "module not found" warnings. +@SuppressWarnings("module") module storm.core { uses st.orm.core.spi.ORMReflectionProvider; uses st.orm.core.spi.ORMConverterProvider;