From e32edd9339ad1f164b37a1d82e30691ea3e1e2e0 Mon Sep 17 00:00:00 2001
From: Vova Kolmakov <wombatukun@apache.org>
Date: Tue, 16 Jun 2026 14:47:41 +0700
Subject: [PATCH] fix(build): declare lombok in annotationProcessorPaths to
 deflake parallel-build compilation

Parallel reactor builds (mvn -T) intermittently fail testCompile with "Provider lombok... could not be instantiated" because the processor is discovered from the shared compile classpath via ServiceLoader. Declaring lombok explicitly in the compiler plugin's annotationProcessorPaths gives each compilation an isolated processor path, removing the race. Lombok is the only annotation processor with work in the build, so no other processing is affected.
---
 pom.xml | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/pom.xml b/pom.xml
index 7e328169b3501..b33e4f9d0f030 100644
--- a/pom.xml
+++ b/pom.xml
@@ -379,6 +379,17 @@
         <configuration>
           <source>${java.version}</source>
           <target>${java.version}</target>
+          <!-- Declare the annotation processor path explicitly instead of relying on classpath
+               service discovery. Lombok is the only annotation processor in the build, and an
+               isolated processor path avoids the flaky "Provider lombok... could not be
+               instantiated" ServiceLoader race seen under parallel (-T) reactor builds. -->
+          <annotationProcessorPaths>
+            <path>
+              <groupId>org.projectlombok</groupId>
+              <artifactId>lombok</artifactId>
+              <version>${lombok.version}</version>
+            </path>
+          </annotationProcessorPaths>
         </configuration>
       </plugin>
       <plugin>