tree 84c5a1aaa82351a00cfe2dbb19bde5e551f5a39d
parent f2abf2692c6c6b56f24a3cb62bc97591da017bb6
author Remi NGUYEN VAN <reminv@google.com> 1613382726 +0900
committer Remi NGUYEN VAN <reminv@google.com> 1613531050 +0900

Do not depend on Tethering stubs in CM consts

Tethering API stubs depend on connectivity stubs for classes like
MacAddress or LinkAddress, so connectivity stubs cannot depend on
Tethering stubs or there would be a circular dependency.

This means ConnectivityManager API surface cannot reference Tethering
API constants. Instead, use the literal in ConnectivityManager.

This means that both ConnectivityManager and TetheringManager specify
the constant value. An alternative considered was to have
TetheringManager depend on the ConnectivityManager constants, but
considering that ConnectivityManager only has some of the constants,
this would be more confusing. Breaking the constants by mistake is
unlikely as their values are part of the API surface, so will always be
in sync.

Bug: 171540887
Test: m
Change-Id: I16b6e1912fffc5ff8b3b392901d2357ffd213c72