History log of /frameworks/support/annotations/src/android/support/annotation/VisibleForTesting.java
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
5dcac27d685f2ac6fd69d0c9bdb984c2a3a1be07 09-Sep-2016 Tor Norbye <tnorbye@google.com> Add metadata for the dimension annotation, and strip typedefs

The support annotations library is a plain Java library, it's not an
Android library, which means it gets built by the Gradle java plugin,
and packaged as a plain jar file. That means that the typedef
annotations (on VisibleForTesting and Dimension) were getting included
in the .jar file, which is pointless.

This CL removes these classes at build time (and to do that, they had
to be top level classes rather than inner classes; removing inner
classes at packaging isn't safe since the outerclass contains
references to its inner classes). This CL also adds external metadata
information about the Dimension's unit attribute, which was missing.

It's unfortunate that we can't just use the android library build
support that handles all this automatically, but a number of users
like that the annotations library is a plain .jar such that they can
include it not just in their Android apps, but in plain Java modules
as well which are contain shared server and app code.

Change-Id: If6ac38f1e5aad7091001ff3749c804b5c0a2452b
/frameworks/support/annotations/src/android/support/annotation/VisibleForTesting.java
6b55d5559e05240c4b8b6693633a40184da1f755 31-Aug-2016 Tor Norbye <tnorbye@google.com> Add production visibility to @VisibleForTesting

This will be used to let lint and Studio for example
highlight when production/non-test code is accessing
APIs outside the intended visibility scope.

191365: Validate @VisibleForTesting actual visibility

Change-Id: I372171aa1df5b4c8bf3e69f492be92dc60d34391
/frameworks/support/annotations/src/android/support/annotation/VisibleForTesting.java
adf6e1d804a89030414d1cba0bde0ca8361ec1c6 04-Dec-2015 Jeff Davidson <jpd@google.com> Make @VisibleForTesting accessible for proguarding.

With only SOURCE retention, proguard can't be configured to keep
anything annotated as @VisibleForTesting, which is one of the major
reasons to use such an annotation in the first place - to prevent code
that's only used in unit tests from being stripped.

Change-Id: Ibe9a098236988001ba17a8c3e7fec52a73db501e
/frameworks/support/annotations/src/android/support/annotation/VisibleForTesting.java
89093da9c4a383a58c2c2de78a2194ac1c020fe7 17-Apr-2015 Stephan Linzner <slinzner@google.com> Added VisibleForTesting annotation

Marks production code that has reduced visibility for testing.

Change-Id: I2dfd82877df805ffad736417005a7b25eb307a07
/frameworks/support/annotations/src/android/support/annotation/VisibleForTesting.java