Tony Robalik

My working assumption is that this is another instance of [this Gradle bug](https://github.com/autonomousapps/dependency-analysis-gradle-plugin/issues/685), except that you say this only appears on 1.30.0 and higher. A reproducer would be very useful.

Thanks for the issue. Can you explain why you have this need to exclude so many things? Is there some issue with the analysis?

> Unless I can exclude projects from onIncorrectConfiguration So you're saying you prefer to have incorrectly declared dependencies? I'm not sure I want to make that easier to do.

I suspect that you might find the bundle feature very useful for meeting your needs. It already permits regex. https://github.com/autonomousapps/dependency-analysis-gradle-plugin/wiki/Customizing-plugin-behavior#logical-dependency-groups-aka-dependency-bundles

Might be able to make use of https://docs.oracle.com/javase/8/docs/api/java/lang/Class.html#isSynthetic-- to filter out the synthetic access properties for purposes of ABI analysis.

Thanks for the report. This might be due to the fact that the plugin depends on Kotlin 1.9.22. Could you try to use that version instead of 1.8?

This feature already exists, partially. See [here](https://github.com/autonomousapps/dependency-analysis-gradle-plugin/blob/512b64db0dc645371337f806c5eeed18c55319bb/src/main/kotlin/com/autonomousapps/model/ModuleAdvice.kt#L34). It uses a heuristic to determine if an Android module "could" or "should" be a JVM module. If you run `./gradlew lib:projectHealth` on...

So this is a feature request to add more logging? Given the nature of that code, I'm not entirely sure logging the unknown byte will be useful, but I suppose...

Hm some logging that indicates the file this trips over might help. I'll add that. Or if you're comfortable debugging, you could do that right now; there are instructions in...

Ok, latest commit adds additional logging so we can see the exact class file this trips over.