Lines Matching refs:files

10 * Allow extracting the API (into signature text files, into stub API files
44     signature files, the SDK stub files, external annotations etc.
75   signature files for the framework as doclava1.
78   means we can regenerate signature files etc for older versions according to
83   IntelliJ external annotations data as well as signature files containing
98     ignores) block comments in the signature files.)
101     files. This is vital now that some of these annotations become part of the
107     their nullness contract, the signature files would very quickly become
133     annotations are not included in signature files) use just the simple name
151 * Support for generating documentation into the stubs files (so we can run
152   javadoc or [Dokka](https://github.com/Kotlin/dokka) on the stubs files instead
158 * Support for parsing Kotlin files. API files can now be implemented in Kotlin
160   is done for Java files.
167   require you to create two signature files to diff.
170   generated the signature files and generated the stubs had diverged, so there
171   was some inconsistency. In metalava the stub files contain **exactly** the
172   same signatures as in the signature files.
179   the exact same API as is listed in the signature files, and once this was
210   (.class or .jar files) and it will then measure the annotation coverage of the
283   annotation files needed by Studio and lint in Gradle, which captures the
295   android.jar files themselves to ensure that it computes the exact available
301   method using the intended visibility instead when generating signature files
315     android.jar files (e.g. backed by bytecode) or reading previous signature
316     files.  Reading in multiple versions of an API lets doclava perform
318     can also generate signature files in the new format (including data that was
319     missing in older signature files, such as annotation methods) without having
336 signature files: TextPackageItem, TextClassItem, and so on.
449 files, which can then be processed by Dokka and Javadoc to generate the same