Tony Robalik

Let me repeat your situation in my own words to verify we're on the same page. You have a method that can throw an exception but doesn't declare that it...

Thanks for the report! Do you happen to have a reproducer? I'm surprised that the unused plugin advice only appears once you exclude the warnings about unused annotation processors. The...

I noticed you have this ```groovy onUsedTransitiveDependencies { // Transitively used dependencies that should be declared directly severity("ignore") } ``` That can lead to advice that _seems_ like false positives...

Added a 1.0 milestone. This issue is important enough that I consider it a prereq for 1.0 status.

@ZacSweers you said > I think a reasonable middle ground is to only ignore them if they only have proguard files included and nothing else. Whereas I was thinking, if...

We discussed this briefly in slack the reason the plugin doesn't support dynamic feature modules is I have never used those, didn't feel like investigating when I was working on...

@meladRaouf I don't know why that would work, do you have a reproducer?

Open request for a minimal reproducer for this! If this issue impacts you, that's what I'll need to provide support.

@ZacSweers could you provide the file `build/reports/dependency-analysis/usages-dependencies.json`, and `build/reports/dependency-analysis/bundled-traces.json`?

I agree with your general idea. Do you want to work on this changed behavior for `compileOnly` dependencies? Secondly, I do want to eventually support `compileOnlyApi`, but care must be...