Lines Matching refs:that

59 flags and translates them on the fly. Flags that are ignored are listed on the
85   load time such that it can be part of the API analysis.
92   * Improve the signature format such that it for example labels enums "enum"
101     files. This is vital now that some of these annotations become part of the
124     names such that you have
137   * Misc documentation handling; for example, it attempts to fix sentences that
138     javadoc will mistreat, such as sentences that "end" with "e.g. ".  It also
153   of the source code). This means that the documentation tool itself does not
156   stub sources that include documentation.
174   (This turned out to be incredibly important; this revealed for example that
180   hooked up to the build it immediately became apparent that it was missing
181   important methods that should really be part of the API.)
184   checks on the public API in the codebase and flag issues that are discouraged
192   records the current set of issues. From that point forward, when metalava
212   that are currently used by a corpus of apps and target our annotation efforts
270   From this it's clear that it would be useful to start annotating
272   unannotated APIs that are frequently used, at least by this app.
275   javadoc, which meant that most of the source tree was opaque. Therefore, as
295   android.jar files themselves to ensure that it computes the exact available
300   method had not required visibility for testing, then metalava will treat that
318     can also generate signature files in the new format (including data that was
338 The "Codebase" class captures a complete API snapshot (including classes that
346 There are several key helpers that help with the implementation, detailed next.
364 which limits itself to visiting code elements that are part of the API.
395 When computing the API, all types that are included in the API should be
441 to flag all API elements that have been removed as invalid (since you cannot