False positive about dependency-analysis-gradle-plugin HOT 2 OPEN

This looks to me like you run into the special treatment of test. The behavior you see is currently expected (it's not a bug).

If something is already implementation, the plugin will advice to not add testImplementation in addition. Because (historically) that is how things are wired in Gradle: testImplementation extend implementation. See: https://docs.gradle.org/current/userguide/java_library_plugin.html#sec:java_library_configurations_graph

However, if you want to look at test as separate "Module", this is counterintuitive. But it depends on how you look at test in your project.

There is a proposal to make this configurable (#900). Meaning, the plugin could introduce an option do disable this special treatment of test. Please have a look at that issue.

Note: This has nothing to do with JPMS. It's the same behavior for any Jar.

I think this can be closed in favor of #900.

from dependency-analysis-gradle-plugin.

Hmm... except Initializer is a compileOnly annotation. So I think the problem is that its scope as implementation is wrong. Sorry, I didn't notice it said "implementation" for that in its detection.

https://github.com/xenoterracide/java-commons/blob/main/module/tools/src/main/java/com/xenoterracide/tools/java/annotation/Initializer.java

annotations are weird, and a bit obnoxious, because even if an annotation were to describe itself as runtime that doesn't mean it should be exposed via api... some annotations like jspecify does that so that runtime tools like spotbugs can see them, but they aren't used beyond tests usually, not real runtime (imho). In this case though I believe this is appropriately defined as a compile only since I didn't specify runtime retention.

from dependency-analysis-gradle-plugin.