apache / apache/maven-dependency-plugin
[MDEP-802] analyze-only fails to recognize `aws-java-sdk-core` as a compile-time dependency
- Dominant language
- Java
- Stars
- 175
- Forks
- 196
- Avg merge
- 19h 30m
- Merged PRs (30d)
- 5
Description
**[Marius Grama](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=JIRAUSER288566)** opened **[MDEP-802](https://issues.apache.org/jira/browse/MDEP-802?redirect=false)** 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:
```
maven-dependency-plugin
com.amazonaws:aws-java-sdk-core
```
Here is the commit showcasing the issue:
https://github.com/trinodb/trino/pull/11550/commits/22f227bb5721b1ea4783c6a58111ef5007f75316
Ideally we'd like not having to deal with this false positive problem.
---
**Affects:** 3.3.0
0 votes, 5 watchers
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the linked Trino commit and the maven-dependency-plugin's analyze-only behavior described in the issue. Trace why an explicitly used class from aws-java-sdk-glue does not cause aws-java-sdk-core to be recognized as compile-time, then reproduce the false positive without the ignoredDependency configuration. Done means the dependency is recognized without requiring that workaround.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100