Tony Robalik

Thanks for the issue. This is an interesting idea, and is why the primary task of the plugin is `buildHealth` and not `findBadDependencies` or something. I'm not sure when I...

Thanks for the issue. There are two kinds of "module advice" related to this: 1. `This project uses limited Android features and could be a JVM project.` 2. `This project...

This has been partially mitigated with https://github.com/autonomousapps/dependency-analysis-gradle-plugin/pull/1438.

Thanks for the issue. The plugin uses a heuristic where it checks the [retention policy](https://docs.oracle.com/javase/8/docs/api/java/lang/annotation/RetentionPolicy.html) on the annotations. If they're all `CLASS` or `SOURCE`, then it says the dependency can...

This is going to be pretty hard to resolve, given current assumptions and implementation. Due to type erasure, when you have a reference like `Class`, the bytecode only contains the...

I actually found a way to do this. The associated PR should resolve this issue 👍

Thanks for the issue. I don't strongly disagree with you. **What I would like, however, is some canonical reference to a JVM spec that discusses this.** The behavior as it...

Thank you, I appreciate the research and detailed information you've provided. I'm inclined to agree with you and open to changing this behavior. However, I also have limited time right...

Thanks for the issue.

> Given that it's not possible to detect whether type-safe accessors are enabled and that it might not be easy to detect the correct DSL, I suggest adding those as...