Text in the documentation is either:
- Used for logging only. (new)
- Disabled for all apps. (new)
- Enabled for all apps. (existing)
- Enabled for apps with targetSdkVersion of greater than X. (existing)

Exempt-From-Owner-Approval: small change local to compat-changes docs

Test: change one change to be logging only, one to be disabled.
Test: m offline-sdk-docs
Test: google-chrome out/target/common/docs/offline-sdk/compatchanges.html
Bug: 148009004
Change-Id: I502f7a55b52b5b74faaf5ed0054a2083e8fad0c2
Merged-In: I502f7a55b52b5b74faaf5ed0054a2083e8fad0c2

We read compat config from an XML file, turn that into a HDF, and then
generate docs using a new template and existing macros as appropriate.
  https://mathewi.users.x20web.corp.google.com/www/compatchanges/offline-sdk/compatchanges.html

Test: m -j offline-sdk-docs
Bug: 144927670
Change-Id: I67dd3662a83538f769aa535979f2119b33e1326e
Exempt-From-Owner-Approval: ag/10107214 approved internally, have Dirk's permission.

Metalava is now generating the API stubs and handles the calculation
of when APIs were introduced and deprecated. It now directly adds this
info to each APIs comment using the tags @apiSince and
@deprecatedSince.

This cl enables the doclava API reference generator to extract these
tags and output them to the docs. Requires passing -metalavaApiSince
into the doclava build.

bug: 125939989
Test: make ds-docs

Change-Id: I1a6c04a3e05dd1dc74ccdaf81ec45b52a40f55fc

We have various "contract" classes across the OS which describe the
columns that are available for insert(), update(), and query() when
working with ContentProviders.

To help ensure that the underlying providers fully support the API
contracts being made, this change defines a new "@Column" annotation
which describes the underlying data type.

These annotations can then be used by the ContentProvider
implementations internally to ensure that they're fully meeting the
API contracts being made.

Bug: 120429729
Test: manual
Change-Id: Iffeb5fce4a1186e0b4aa3424ecb69a34f6607c21

Bug: 78064247
Test: none
Change-Id: Ic43172d135b26698192144b6c6f8e070bb318886

The non-escaped spaces have been a long-standing issue that created
incompatible behaviors on the new devsite design. Escaping these is the
right thing to do, but yes, it will break some existing links that use
the old URLs with actual spaces. We'll need to resolve those over time.

Using the <a> tags resulted in bad vertical positioning, so this now puts the
anchor name in the header tag with the id attribute.

Also lots of removal of legacy "apilevel" class names, and addition
of the data attribute where it was still missing.

bug: 79995820 (escape spaces)
bug: 80256515 (remove "apilevel" classes)

test: make ds-docs
sample of results at cl/197951140

Change-Id: I038cd4abfdd498f82740aeb149cbaabd252d3ff1

am: dff2ae6578

Change-Id: Iea9dc69057bdf2070bb0cd1138032db25f416bcc

(irina)

- Stop calling legacy writeNavTree() method that generates JS files
- Stop printing HTML list of sibling TOC items at the end of class page
- Stop generating an index.html page that redirects to the classes page
- Start using _toc.yaml filename by default, instead of _book.yaml

bug: 79155333
Change-Id: I445a96567a131bb04d8e9485b7fd41879089fb23