8af11a980a
In most cases, the places that were trying to avoid a transitive dependency on `lib-exoplayer` when this duplication was introduced [1] are already depending on it again, except for `lib-container` where the dep is added in this change. In general it seems fine for the tests of module A to depend (transitively or directly) on module B even where the prod code of module A **does not** depend on module B. [1] <unknown commit> PiperOrigin-RevId: 561660371
Container module
Provides functionality for media containers.
Getting the module
The easiest way to get the module is to add it as a gradle dependency:
implementation 'androidx.media3:media3-container:1.X.X'
where 1.X.X is the version, which must match the version of the other media
modules being used.
Alternatively, you can clone this GitHub project and depend on the module locally. Instructions for doing this can be found in the top level README.