pom.xml missing dependencies

[kanwhoa]

Describe the bug

In the current version (2.6.3), the pom.xml file appears to be empty, i.e. missing runtime dependencies. In comparison to 2.6.2 where the runtime dependencies were included. This breaks systems based on Maven. The .module file appears correct.

Expected Behavior

Th pom.xml file should include the appropriate run/compile time dependencies.

What plugins are used? What other connection properties were set?

N/A

Current Behavior

Our build failed to include the relevant runtime dependencies.

Reproduction Steps

Create a project using the following pom.xml using maven. This will compile, however, when creating uber-jars (for example through Spring Boot), the required runtime dependencies are not included.

<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
  <modelVersion>4.0.0</modelVersion>

  <artifactId>test</artifactId>
  <groupId>test</groupId>
  <version>1.0.0-SNAPSHOT</version>
  <packaging>jar</packaging>

  <name>Example project</name>
  <dependencies>
    <dependency>
      <groupId>software.amazon.jdbc</groupId>
      <artifactId>aws-advanced-jdbc-wrapper</artifactId>
      <version>LATEST</version>
    </dependency>
  </dependencies>
</project>

Possible Solution

No response

Additional Information/Context

No response

The AWS Advanced JDBC Driver version used

2.6.3

JDK version used

openjdk 21.0.7 2025-04-15

Operating System and version

OSX

[ccayg-sainsburys]

Introduced by #1517
@sergiyvamz / @karenc-bq are you able to help here?

[sergiyvamz]

Hi @kanwhoa

Previous versions of the AWS JDBC Driver (up to 2.6.2) included incorrect required runtime dependencies (AWS SDK and org.apache.httpcomponents). The latest version of the driver (2.6.3) resolves this issue by removing these dependencies. The driver now has no required runtime dependencies. Certain driver configurations may require additional runtime dependencies (such as the AWS SDK), which are documented accordingly.

It appears that the dependency issue has been resolved in the pom.xml file but not in the module file. To confirm the scope of this issue: aside from the discrepancy between the pom.xml and module files, are there any runtime issues when running the uber jar as mentioned above?

[ccayg-sainsburys]

Not the original poster but at least for us we saw
Required dependency AWS Java SDK RDS v2.x is not on the classpath.

I appreciate (now) this is documented (and also here)

But I think the change at #1517 could either have been more than a patch release or called out more clearly in the release notes as it was a breaking change even if that was because we were relying on unintended functionality in version 2.6.2

[phrabec]

This change introduced a clear breaking change; dependencies that were present from 2.3.3 through 2.6.2 are now missing from the published POM. If the intent were to avoid pulling in heavy libraries by default, the correct approach would have been to mark them as optional, rather than stripping all <dependency> entries. Documentation is not a fix for missing package manager metadata. Publishing an empty POM not only breaks standard Maven usage but also violates expectations for a patch release, where backward compatibility should be preserved. Such an impactful change should be at least a minor release, not a patch.

[timhamoni]

Thanks for the clarification, if these really not required, then it makes sense for them to go away. We are including the RDS dependency with the HttpComponents transport and hence source of this discussion.

Can I suggest an approach that might clean up the above comments. In Gradle, additional variants can be published, so a variant called mariadbRuntimeElements might publish a set of runtime dependencies on the MariaDB library, and mariadbRdsRuntimeElements might include the MaraiDB library, and the RDS library as runtime components. This would allow consumers to depend on the variant for their platform, and it would pull the correct version of the database and AWS libraries that this project was build/tested against.

In Maven, this isn't so clean. The simplest way would be to map these optional dependencies with a runtime scope. Using profiles would be the most aligned with Gradle variants, however, the activation would need to be determined which I presume would be by property.

[sergiyvamz]

Hi @kanwhoa @ccayg-sainsburys @phrabec @timhamoni

We have just merged in a fix. Could you kindly checkout our snapshot build and let us know if the issue still persists?

If everything looks fine we'll release the fix shortly.

Thank you!

[timhamoni]

Thanks, the pom.xml looks fine. The Gradle .module file is correct, but unless I'm mistaken, there's no-way to select that variant. Gradle does not perform matching by name, so it needs some custom attribute to select.

I.e. the module would need something like

{
      "name": "optionalRuntimeElements",
      "attributes": {
        "org.gradle.category": "library",
        "org.gradle.dependency.bundling": "external",
        "org.gradle.jvm.version": 8,
        "org.gradle.libraryelements": "jar",
        "org.gradle.usage": "java-runtime",
        "software.amazon.jdbc.aws-advanced-jdbc-wrapper.optional": true,
      },
      ...
}

Then in the build.gradle, a consumer can do:

runtimeOnly("software.amazon.jdbc:aws-advanced-jdbc-wrapper:+") {
        attributes {
            attribute(Attribute.of("software.amazon.jdbc.aws-advanced-jdbc-wrapper.optional", Boolean.class), true)
        }
}

At least that's how I believe it works. Please correct me if I'm wrong (btw, @kanwhoa is also me, sorry for the confusion).

[sergiyvamz]

Hi @timhamoni

Here is a post about variant usage in Gradle: https://blog.gradle.org/optional-dependencies
I believe the correct dependency declaration should be structured as follows:

dependencies {
    implementation("software.amazon.jdbc:aws-advanced-jdbc-wrapper:+") {
        capabilities {
           requireCapability("software.amazon.jdbc:aws-advanced-jdbc-wrapper-optional")
        }
    }
}

Does this resolve the concerns regarding the driver's optional dependencies?

[timhamoni]

Thanks, much appreciated. It's a much cleaner way to handle now 🙇🙇

[karenc-bq]

Hi all, the fix is now available in v2.6.4. We will close this issue now.

Thank you all again for raising this, please feel free to reach out again if you encounter any other issues.