[jira] [Commented] (MDEP-846) Source-only dependencies are not detected

["Richard Eckart de Castilho (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MDEP-846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17702795#comment-17702795 ] 

Richard Eckart de Castilho commented on MDEP-846:
-------------------------------------------------

I guess the only way to fix this issue would be introducing another analyzer implementation which would look at the source files. Currently (1.13.0), the only implementation of the `ClassAnalyzer` interface is based on ASM (i.e. on inspecting class files).

> Source-only dependencies are not detected
> -----------------------------------------
>
>                 Key: MDEP-846
>                 URL: https://issues.apache.org/jira/browse/MDEP-846
>             Project: Maven Dependency Plugin
>          Issue Type: Bug
>            Reporter: Richard Eckart de Castilho
>            Priority: Major
>
> 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.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)