[MDEP-646] mvn dependency:analyze mistakenly treat backward compatible classes as used undeclared

**[John Lin](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=johnlinp)** opened **[MDEP-646](https://issues.apache.org/jira/browse/MDEP-646?redirect=false)** and commented

I have the following dependency in my `pom.xml`:

```

org.apache.cassandra
cassandra-all
2.1.8

```

Then a piece of code in my app:

```
import java.util.concurrent.ConcurrentHashMap;

public class App {
public void foo () {
ConcurrentHashMap m = new ConcurrentHashMap<>();
...
}
}
```

Then `mvn dependency:analyze` will find a used undeclared dependency:

```
[WARNING] Used undeclared dependencies found:
[WARNING] com.boundary:high-scale-lib:jar:1.0.6:compile
```

It turns out that `cassandra-all` has a dependency on `high-scale-lib`, and `high-scale-lib` implemented a `java.util.concurrent.ConcurrentHashMap` for backward compatibility.

In fact, my app use the built-in `ConcurrentHashMap` in JDK, not the `ConcurrentHashMap` from `high-scale-lib`. So I believe that it is incorrect for the dependency analysis to report it as used.

---

**Affects:** 3.1.1

Reproduce the report with the pom.xml dependency on org.apache.cassandra:cassandra-all:2.1.8 and the App example using java.util.concurrent.ConcurrentHashMap, then run mvn dependency:analyze. Compare the JDK class with high-scale-lib's backward-compatible class and trace why the analyzer treats the transitive dependency as used. Done means the built-in JDK usage is no longer reported as an undeclared high-scale-lib dependency.

Written by the indexing model from the issue text.