[MDEP-846] Source-only dependencies are not detected

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: analyze
• Assignee: Unassigned
• Reporter: Richard Eckart de Castilho
• Created: 20/Mar/23 15:13
• Updated: 20/Mar/23 15:38

Description

If a class in the `src/main/java` part module A has a source-only dependency on a class in module B, the dependency dependency of A to B is not detected. This can lead to build failures if any class in the `src/main/test` part of module A also has dependencies on module B as the analyzer claims that the dependency of module B should be moved to the `test` scope. Doing so - however - then breaks the build.

One such source-only dependency would be the import of a compile-time constant (e.g. static final String = "XXX") from a class in module B. Such constants are inlined into the class file produced for the class of module A. Thus, the compile-time dependency on module B cannot be determined by inspecting the class file using ASM.

Issue Links

• duplicates: MSHARED-1211 Source-only dependencies are not detected