Lines Matching refs:files

8 1. The format emitted by doclava, and used for Android's signature files up
10    over time, so older signature files vary a bit (many of these changes were
37 That means the annotations should be part of the signature files too -- such
55 New signature files (v2+) generally include a file header comment which states
57 signature files. For example, in v3 the type "String" means "@NonNull String",
157 With these changes, these lines from v1 signature files:
180 The v1 signature files uses raw types in some places but not others.  Note that
251 This doesn't currently apply to the SDK, but the signature files are also used
268 syntax. Therefore, we need to also capture properties in the signature files. If
276 it will get recorded in the signature files like this:
300 In v1 files we only list type names, but in v2 we allow an optional parameter
347 Doclava did not include these methods in the signature files, but they **were**
348 present in the stub files (and therefore part of the API). In the v2 signature
352 files, that method does not exist, but clearly it's there in the SDK. The reason
359 Doclava always inserted two special methods in the signature files for every
374 files since they're entirely implied by the enum, you can't change them, and
464 In Java files, you can implicitly reference classes in java.lang without
465 importing them. In v2 offer the same thing in signature files. There are several
473 signature files, and implicitly adding it back when reading in signature files.
513 For example, to update all the signature files to v3, run this command: