122916999: Compat check with *current: ensure no file diffs
When running compatibility checks against current.txt, system-current.txt etc, also require that the signature file itself has not changed. This is necessary since there are many changes you can make which are visible in the signature file but compatible, and we want these to show up immediately such that they don't accumulate and show up as diffs for the next engineer who makes an incompatible change. Fixes: 122916999 Test: Unit test included Change-Id: Iae62cd1ccb706e888b83d9fe41395d4775795e57
Showing
- src/main/java/com/android/tools/metalava/ApiType.kt 22 additions, 0 deletionssrc/main/java/com/android/tools/metalava/ApiType.kt
- src/main/java/com/android/tools/metalava/Diff.kt 139 additions, 0 deletionssrc/main/java/com/android/tools/metalava/Diff.kt
- src/main/java/com/android/tools/metalava/Driver.kt 32 additions, 12 deletionssrc/main/java/com/android/tools/metalava/Driver.kt
- src/main/java/com/android/tools/metalava/Options.kt 13 additions, 0 deletionssrc/main/java/com/android/tools/metalava/Options.kt
- src/test/java/com/android/tools/metalava/ApiFromTextTest.kt 1 addition, 1 deletionsrc/test/java/com/android/tools/metalava/ApiFromTextTest.kt
- src/test/java/com/android/tools/metalava/CompatibilityCheckTest.kt 53 additions, 0 deletions...java/com/android/tools/metalava/CompatibilityCheckTest.kt
- src/test/java/com/android/tools/metalava/DriverTest.kt 19 additions, 4 deletionssrc/test/java/com/android/tools/metalava/DriverTest.kt
Loading
Please register or sign in to comment