From 276cfbe6551270d45c1a8ff6303cf0f88d4cfa7d Mon Sep 17 00:00:00 2001
From: Raffi Khatchadourian <khatchad@hunter.cuny.edu>
Date: Wed, 29 Apr 2026 09:51:04 -0400
Subject: [PATCH] Use `${maven.multiModuleProjectDirectory}/spotless.xml.prefs`
 for robust resolution
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

The relative `./spotless.xml.prefs` path resolves correctly when Maven
is invoked from the multi-module root, but can fail when invoked from
elsewhere (e.g., a submodule's `basedir`, an IDE's per-module run, or
nested Maven invocations). Switching to the
`${maven.multiModuleProjectDirectory}` property — which always points
at the directory containing the parent `pom.xml` — makes resolution
robust regardless of invocation context.

Matches the pattern downstream consumers like
`ponder-lab/Hybridize-Functions-Refactoring` already use for the same
file. Verified `mvn spotless:check` and
`mvn -pl com.ibm.wala.cast.python.ml spotless:check` both succeed
after the change.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
---
 pom.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/pom.xml b/pom.xml
index e5b9e03b0..3bb608c97 100644
--- a/pom.xml
+++ b/pom.xml
@@ -242,7 +242,7 @@
                 <eclipseWtp>
                   <type>XML</type>
                   <files>
-                    <file>./spotless.xml.prefs</file>
+                    <file>${maven.multiModuleProjectDirectory}/spotless.xml.prefs</file>
                   </files>
                 </eclipseWtp>
                 <trimTrailingWhitespace/>