Lines Matching refs:from
61 metalava extracts metadata from source code to generate artifacts such as the
78 * Ability to read in an existing android.jar file instead of from source, which
83 * Ability to merge in data (annotations etc) from external sources, such as
124 and reinsert during import. Specifically, drop "java.lang." from package
148 in from external sources, but also inferring whether nullness annotations have
160 as well and metalava will parse and extract API information from them just as
166 (e.g. you can change a parameter from non null to nullable for final classes,
176 StringBuilder.setLength(int) was missing from the API signatures since it is a
177 public method inherited from a package protected super class, which the API
300 from the support library, where you can express the intended visibility if the
315 a model not just from parsing source code, but from reading older SDK
342 There are methods to load codebases - from source folders, from a .jar file,
343 from a signature file. That's how API diffing is performed: you load two
344 codebases (from whatever source you want, typically a previous API signature
454 docs (such as documenting permissions, ranges and typedefs from annotations) was