From a794040efa4c8d83e58cd31171963972d4f10807 Mon Sep 17 00:00:00 2001
From: Vikrant Puppala <vikrant.puppala@databricks.com>
Date: Tue, 28 Apr 2026 17:54:41 +0000
Subject: [PATCH] Fix unresolvable 3.3.2 Maven Central POM for uber jar
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

The uber jar's published POM declared a compile dependency on the
internal databricks-jdbc-core coordinate, which is never published to
Maven Central. Downstream consumers bumping to 3.3.2 saw:

  Could not find artifact com.databricks:databricks-jdbc-core:jar:3.3.2

Root cause: flatten-maven-plugin's <dependencies>expand</dependencies>
rewrites direct + transitive deps to a flat list, but does not drop a
direct dep that points at an unpublished sibling module. The shaded
uber jar contains every runtime class, so the published POM should
declare zero compile deps — switch flatten to <dependencies>remove</dependencies>.

Verified by re-running the release-workflow build sequence locally and
resolving com.databricks:databricks-jdbc:3.3.2 against a repo that
omits both jdbc-core and the parent POM (mimicking Maven Central state).
With the fix, resolution succeeds; without it, it fails identically to
issue #1431.

Fixes #1431

Co-authored-by: Isaac
Signed-off-by: Vikrant Puppala <vikrant.puppala@databricks.com>
---
 NEXT_CHANGELOG.md     | 5 +++++
 assembly-uber/pom.xml | 9 ++++++++-
 2 files changed, 13 insertions(+), 1 deletion(-)

diff --git a/NEXT_CHANGELOG.md b/NEXT_CHANGELOG.md
index d27a25e263..aadc3f892a 100644
--- a/NEXT_CHANGELOG.md
+++ b/NEXT_CHANGELOG.md
@@ -8,6 +8,11 @@
 
 ### Fixed
 
+- Fix unresolvable Maven Central POM for the uber JAR. The published POM no longer
+  declares a transitive dependency on the internal `databricks-jdbc-core` coordinate
+  (which is not published to Maven Central), restoring resolution for downstream
+  consumers (#1431).
+
 ---
 *Note: When making changes, please add your change under the appropriate section
 with a brief description.*
diff --git a/assembly-uber/pom.xml b/assembly-uber/pom.xml
index 50f02110d2..889f2b997a 100644
--- a/assembly-uber/pom.xml
+++ b/assembly-uber/pom.xml
@@ -61,6 +61,13 @@
 
     <build>
         <plugins>
+            <!-- flatten-maven-plugin produces .flattened-pom.xml: a self-contained
+                 POM with the parent reference inlined and all <dependencies> stripped.
+                 The shaded uber jar bundles every runtime dep, so the published POM
+                 must declare zero compile deps; otherwise consumers transitively pull
+                 the internal databricks-jdbc-core coordinate (which is not published
+                 to Maven Central) and resolution fails. The release workflow uploads
+                 .flattened-pom.xml as the published POM. -->
             <plugin>
                 <groupId>org.codehaus.mojo</groupId>
                 <artifactId>flatten-maven-plugin</artifactId>
@@ -69,7 +76,7 @@
                     <updatePomFile>true</updatePomFile>
                     <flattenMode>oss</flattenMode>
                     <pomElements>
-                        <dependencies>expand</dependencies>
+                        <dependencies>remove</dependencies>
                         <build>remove</build>
                     </pomElements>
                 </configuration>