[MSHARED-1212] Detection that class is required in compile scope not happening because class only used as generic type

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: maven-dependency-analyzer-1.13.0
• Component/s: maven-dependency-analyzer
• Assignee: Unassigned
• Reporter: Richard Eckart de Castilho
• Created: 20/Mar/23 17:05
• Updated: 20/Mar/23 17:05

Description

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.