Tyler Wong

By default the source path is set to `src`. If a more granular subdirectory is set by the Gradle plugin such as `sourcePaths.setFrom("src/main")`, then anything from the test source set...

Added some upcoming changes in [54ce413](https://github.com/tylerbwong/metalava-gradle/commit/54ce413e15c259aa4e532bfec7e1635e081510df). Source sets should be detected automatically based on what type of module the plugin is being applied to (excluding test sources by default). The...

~~I was able to reproduce with the current version of the plugin. I _think_ this will be fixed by #35. I wasn't able to reproduce locally while testing on that...

It seems this is being done within the Metalava tool. When parsing the flag for `--api`, [`stringToNewFile` is used](https://cs.android.com/android/platform/superproject/+/master:tools/metalava/src/main/java/com/android/tools/metalava/Options.kt;l=820) which always deletes the previous file if it exists.

Hey @liutikas any thoughts about this?

Hm, I'm wondering if it's passing because it doesn't consider adding an annotation a breaking API change? Does the check compatibility task still pass for a removed or added parameter?

@liutikas I haven't gotten a chance to dive into the changes in alpha09, but is this supported? Or is it already supported?

Currently have a CL open to add support this in the main project: https://android-review.googlesource.com/c/platform/tools/metalava/+/3139013 #95 is a sample of what the config option would look like in practice.

This will be available in the next release.

Looks good to me! Just need to run `./gradlew metalavaGenerateSignature` to update the API files.