From 0528ba666ec5fc119611f0a103522db7812652b8 Mon Sep 17 00:00:00 2001
From: 1fanwang <1fannnw@gmail.com>
Date: Sun, 30 Aug 2026 10:05:24 -0400
Subject: [PATCH] GH-3682: Record an explicit revision when building from a
 source release

The ASF source release is a `git archive`, so it has no .git directory.
buildnumber-maven-plugin leaves buildNumber unset, and tarball builds
ship `(build ${buildNumber})` and a blank `git-SHA-1` entry, so they
cannot report what they were built from.

Set the plugin's existing revisionOnScmFailure so they record `unknown`.
Git checkouts still report the real commit.

Signed-off-by: 1fanwang <1fannnw@gmail.com>
---
 pom.xml | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/pom.xml b/pom.xml
index d190b3b67a..c7914c2c48 100644
--- a/pom.xml
+++ b/pom.xml
@@ -524,6 +524,11 @@
         <artifactId>buildnumber-maven-plugin</artifactId>
         <!-- Warning! 3.2.1 caused issues during verification, 3.2.0 is known to work correctly. -->
         <version>3.2.0</version>
+        <configuration>
+          <!-- Source distributions carry no .git metadata, so the revision cannot be read.
+               Record an explicit value instead of leaving ${buildNumber} unresolved. -->
+          <revisionOnScmFailure>unknown</revisionOnScmFailure>
+        </configuration>
         <executions>
           <execution>
             <phase>validate</phase>