[MDEP-679] mvn dependency:analyze detected wrong transitive dependency

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 3.1.1
• Fix Version/s: 3.3.0
• Component/s: analyze
• Labels: S2
• Assignee: Slawomir Jaranowski
• Reporter: John Lin
• Created: 09/Mar/20 10:14
• Updated: 29/Jan/22 14:39
• Resolved: 29/Jan/22 14:39

Description

To illustrate this issue, I created a sample project here: https://github.com/johnlinp/misc-demo/tree/master/maven-dependency-analyze-dnsjava

The dependency tree is like this:

My app ---> ApacheJMeter_http ---> dnsjava

I didn't use any code directly from the artifact dnsjava in my app. I only used ApacheJMeter_http. However, the command mvn dependency:analyze will report a used undeclared dependency: dnsjava.

[INFO] --- maven-dependency-plugin:3.1.1:analyze (default-cli) @ maven-dependency-analyze-dnsjava ---
[WARNING] Used undeclared dependencies found:
[WARNING]    dnsjava:dnsjava:jar:2.1.9:runtime 

It seems that the problem came from the line:

map.put("update", null);

If I change it into map.put("create", null); or even map.put("UPDATE", null);, the problem will disappear. Therefore, I think there might be something to do with the string "update".

Note that this issue is not reproducible in maven-dependency-plugin:2.8.

Issue Links

• is blocked by: MSHARED-1023 dependency:analyze detected wrong transitive dependency
• is blocked by: MDEP-784 Upgrade maven-dependency-analyzer to 1.12.0
• is caused by: MDEP-471 Java 8 Method references are not detected