| commit | 754e40e8d6ec870a8691d97c562e7e24ad56b2a8 | [log] [tgz] |
|---|---|---|
| author | Thiébaud Weksteen <tweek@google.com> | Wed May 25 12:02:13 2022 +1000 |
| committer | Thiébaud Weksteen <tweek@google.com> | Mon Sep 26 04:13:02 2022 +0000 |
| tree | 8c05d3a4f4783b74a5b11cc14fec7510f78ef94a | |
| parent | e48e2f74429e7e163d420129a8da247391d2f4a2 [diff] |
Remove support of @EnforcePermission on classes The intent of the @EnforcePermission annotation is to visually indicate that permissions have already been verified. When applied to a class, the visual indication is far from the actual implementation (method). Only accept the annotation on methods instead of any type. This annotation has recently been introduced for platform services only. There are no instances of such class annotation in AOSP. Test: build Change-Id: I2d6a747cc41badf5ce8788986a4434ed7add0790
Libraries and utilities intended for use by module and framework code.
Since modules use the code in this project, it must adhere to mainline requirements, for example, by setting min_sdk_version in Soong modules.
This project uses a single source path for Java code. All Java code should go in the java directory with subdirectories corresponding to the java package. Android.bp files should go alongside the java source files, and should only include java source for a single java package to encourage good code hygiene.
Tests for java code should go in the javatests directory and follow the same structure.