Marius Grama opened MDEP-802 and commented
The maven-dependency-plugin fails to recognize aws-java-sdk-core as a compile-time dependency, because we only explicitly use a class from aws-java-sdk-glue, which in turn extends from a class from aws-java-sdk-core.
In order to cope with this problem, we set aws-java-sdk-core as an ignored dependency:
<artifactId>maven-dependency-plugin</artifactId>
<configuration>
<ignoredNonTestScopedDependencies>
<!-- dependency plugin fails to recognize aws-java-sdk-core as a compile-time dependency, because
we only explicitly use a class from aws-java-sdk-glue, which in turn extends from a class from
aws-java-sdk-core -->
<ignoredDependency>com.amazonaws:aws-java-sdk-core</ignoredDependency>
</ignoredNonTestScopedDependencies>
</configuration>
</plugin>
Here is the commit showcasing the issue:
trinodb/trino@22f227b
Ideally we'd like not having to deal with this false positive problem.
Affects: 3.3.0
0 votes, 5 watchers
Marius Grama opened MDEP-802 and commented
The maven-dependency-plugin fails to recognize
aws-java-sdk-coreas a compile-time dependency, because we only explicitly use a class fromaws-java-sdk-glue, which in turn extends from a class fromaws-java-sdk-core.In order to cope with this problem, we set
aws-java-sdk-coreas an ignored dependency:Here is the commit showcasing the issue:
trinodb/trino@22f227b
Ideally we'd like not having to deal with this false positive problem.
Affects: 3.3.0
0 votes, 5 watchers