fix jedis-compatibility publishing configuration

- Update GPG signing key ring file path from jedis-compatibility/secring.gpg to secring.gpg in CI workflow
- Add explicit jar packaging declaration to Maven POM configuration
- Align publishing paths with project structure for consistent artifact generation

Signed-off-by: affonsov <67347924+affonsov@users.noreply.github.com>

Author: affonsov

.github/workflows/java-cd.yml

@@ -340,7 +340,7 @@ jobs:
               run: |
                   ./gradlew --build-cache :jedis-compatibility:publishToMavenLocal \
                   -x buildRust \
-                  -Psigning.secretKeyRingFile=jedis-compatibility/secring.gpg \
+                  -Psigning.secretKeyRingFile=secring.gpg \
                   -Psigning.password="${{ secrets.GPG_PASSWORD }}" \
                   -Psigning.keyId=${{ secrets.GPG_KEY_ID }}
 

java/jedis-compatibility/build.gradle

@@ -113,6 +113,7 @@ publishing {
             artifactId = 'valkey-glide-jedis-compatibility'
             version = System.getenv("GLIDE_RELEASE_VERSION") ?: project.ext.defaultReleaseVersion
             pom {
+                packaging = 'jar'
                 name = 'valkey-glide-jedis-compatibility'
                 description = 'Jedis compatibility layer for Valkey GLIDE'
                 url = 'https://github.com/valkey-io/valkey-glide.git'