Richard Eckart de Castilho opened MSHARED-1212 and commented
Let's say we have a class in module A which calls a method List<MyObject> getList() from module B. The class MyObject comes from module C.
Also, there is some test class in module A which uses MyObject.
Eclipse will fail to compile this unless MyObject is in the compile scope.
The dependency analyzer will, however, not detect that MyObject is required in the compile scope because the class file for A does not contain a reference to MyObject (due to generic type erasure) and will indicate that module C/MyObject should be in scope test.
Affects: maven-dependency-analyzer-1.13.0