5 Commits

Author	SHA1	Message	Date
olly	1bf53bfabc	Refine ProGuard config workaround for Function ... This is a more targeted workaround, which still allows for the containing package name to be obfuscated. #minor-release PiperOrigin-RevId: 355381201	2021-02-03 15:03:07 +00:00
olly	b1920f3a78	Fix ProGuard configuration for 2.13 ... Note: We only support pro-guard on a best effort basis, and developers should use R8 whenever possible. #minor-release PiperOrigin-RevId: 355129695	2021-02-02 13:06:52 +00:00
ibaker	50566fb8ac	Suppress ProGuard warnings related to Guava's compile-only deps ... Without these lines, ProGuard fails on the demo app (R8 works). Also include some more `-dontwarn` lines from https://github.com/google/guava/wiki/UsingProGuardWithGuava #minor-release Issue: #8103 PiperOrigin-RevId: 339050634	2020-11-02 22:56:21 +00:00
ibaker	70ebe12ef9	Suppress Guava-related ProGuard/R8 warnings ... I didn't copy-paste the whole of https://github.com/google/guava/wiki/UsingProGuardWithGuava because this line seems relevant based on our current usage. Lots of that file seems to relate to classes that are strongly discouraged on Android: https://github.com/google/guava/wiki/Android#specifics I've only added this to the `common` module, since everyone that uses ExoPlayer must depend on that. This avoids duplicating this line into every module that has a Guava dependency. Also remove some other warning suppressions that are defined in both `core` and `common`. Issue: #7904 PiperOrigin-RevId: 332203086	2020-09-17 17:41:34 +01:00
andrewlewis	91517dc957	Split out extractor and common modules ... PiperOrigin-RevId: 291378636	2020-01-24 18:15:19 +00:00