History log of /frameworks/support/annotations/src/android/support/annotation/RestrictTo.java
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
9737488834b24e1f8b3e268e32d2662f1a0eb415 05-Nov-2016 Tor Norbye <tnorbye@google.com> Add RestrictTo scope for the same library

This will allow a single library to have public implementation classes
that can be referenced from other packages within the same library,
but without exposing them to other libraries in the same group.

Also added an alias for GROUP_ID called LIBRARY_GROUP since I think it
reads better than GROUP_ID in code, and pairs better with
LIBRARY. (The alternative was to use ARTIFACT_ID for the new library
scope, but that didn't seem right (and we really want to match *both*
group id and artifact id, not just the latter.)

Test: The new annotation scope and the aliasing of GROUP_ID and
LIBRARY_GROUP is checked by lint unit tests in lint's codebase.

Change-Id: I909106ceba8712e0923dc9ae865d36609fb270e2
/frameworks/support/annotations/src/android/support/annotation/RestrictTo.java
e534c663bb922f6b126f51b3cee805effbfb2404 22-Aug-2016 Alan Viverette <alanv@google.com> Initial implementation for RestrictTo annotation

Bug: 27937193
Change-Id: I4479d055121ca2bb42bfc09a61feebaed960d251
/frameworks/support/annotations/src/android/support/annotation/RestrictTo.java