correct approach

Author: shivam2680

.github/workflows/release.yml

@@ -38,10 +38,25 @@ jobs:
           MAVEN_CENTRAL_USERNAME: ${{ secrets.MAVEN_CENTRAL_USERNAME }}
           MAVEN_CENTRAL_PASSWORD: ${{ secrets.MAVEN_CENTRAL_PASSWORD }}
 
-      - name: Generate and Deploy Thin JAR
+      - name: Deploy Thin JAR (Simple approach)
         run: |
-          # Deploy thin JAR as a separate artifact to the same staging repository
-          ./release-thin-jar.sh
+          # Get version from POM
+          VERSION=$(grep -m1 '<version>' pom.xml | sed 's/.*<version>\(.*\)<\/version>.*/\1/')
+          echo "Deploying thin JAR version: $VERSION"
+          
+          # Update version in thin_public_pom.xml
+          sed -i "s/<version>.*<\/version>/<version>$VERSION<\/version>/" thin_public_pom.xml
+          
+          # Thin JAR already exists from main build - just deploy it with different POM
+          mvn gpg:sign-and-deploy-file \
+            -Dfile="target/databricks-jdbc-${VERSION}-thin.jar" \
+            -DpomFile=thin_public_pom.xml \
+            -DrepositoryId=central \
+            -Durl=https://oss.sonatype.org/service/local/staging/deploy/maven2/ \
+            -DgroupId=com.databricks \
+            -DartifactId=databricks-jdbc-thin \
+            -Dversion="$VERSION" \
+            -Dpackaging=jar
         env:
           GPG_PASSPHRASE: ${{ secrets.GPG_PASSPHRASE }}
           MAVEN_CENTRAL_USERNAME: ${{ secrets.MAVEN_CENTRAL_USERNAME }}

README.md

@@ -24,16 +24,39 @@ Add the following dependency to your `pom.xml`:
 </dependency>
 ```
 
+#### Thin JAR
+
+For applications requiring explicit dependency management, use the thin JAR variant:
+
+```xml
+<dependency>
+  <groupId>com.databricks</groupId>
+  <artifactId>databricks-jdbc-thin</artifactId>
+  <version>1.0.9-oss</version>
+</dependency>
+```
+
+The thin JAR contains only the driver code and declares all dependencies in its POM, enabling dependency introspection and version management.
+
 ### Build from Source
 
 1. Clone the repository
 2. Run the following command:
    ```bash
    mvn clean package
    ```
-3. The jar file is generated as `target/databricks-jdbc-<version>.jar`
+3. The following JAR files are generated:
+   - `target/databricks-jdbc-<version>.jar` (standard JAR with bundled dependencies)
+   - `target/databricks-jdbc-<version>-thin.jar` (thin JAR without dependencies)
 4. The test coverage report is generated in `target/site/jacoco/index.html`
 
+To install the thin JAR locally with dependency metadata:
+```bash
+VERSION=$(grep -m1 '<version>' pom.xml | sed 's/.*<version>\(.*\)<\/version>.*/\1/')
+sed -i "s/<version>.*<\/version>/<version>$VERSION<\/version>/" thin_public_pom.xml
+mvn install:install-file -Dfile="target/databricks-jdbc-${VERSION}-thin.jar" -DpomFile=thin_public_pom.xml
+```
+
 ## Usage
 
 ### Connection String