@@ -9,37 +9,37 @@ and extend, and can be updated through Play Store application updates.
99
1010## Documentation ##
1111
12- * The [ developer guide] [ ] provides a wealth of information to help you get
13- started.
14- * The [ class reference] [ ] documents the ExoPlayer library classes.
12+ * The [ developer guide] [ ] provides a wealth of information.
13+ * The [ class reference] [ ] documents ExoPlayer classes.
1514* The [ release notes] [ ] document the major changes in each release.
15+ * Follow our [ developer blog] [ ] to keep up to date with the latest ExoPlayer
16+ developments!
1617
1718[ developer guide ] : https://google.github.io/ExoPlayer/guide.html
1819[ class reference ] : https://google.github.io/ExoPlayer/doc/reference
19- [ release notes ] : https://github.com/google/ExoPlayer/blob/dev-v2/RELEASENOTES.md
20+ [ release notes ] : https://github.com/google/ExoPlayer/blob/release-v2/RELEASENOTES.md
21+ [ developer blog ] : https://medium.com/google-exoplayer
2022
2123## Using ExoPlayer ##
2224
23- ExoPlayer modules can be obtained via JCenter. It's also possible to clone the
25+ ExoPlayer modules can be obtained from JCenter. It's also possible to clone the
2426repository and depend on the modules locally.
2527
26- ### Via JCenter ###
28+ ### From JCenter ###
2729
2830The easiest way to get started using ExoPlayer is to add it as a gradle
29- dependency. You need to make sure you have the JCenter and Google Maven
30- repositories included in the ` build.gradle ` file in the root of your project:
31+ dependency. You need to make sure you have the JCenter and Google repositories
32+ included in the ` build.gradle ` file in the root of your project:
3133
3234``` gradle
3335repositories {
3436 jcenter()
35- maven {
36- url "https://maven.google.com"
37- }
37+ google()
3838}
3939```
4040
4141Next add a gradle compile dependency to the ` build.gradle ` file of your app
42- module. The following will add a dependency to the full ExoPlayer library:
42+ module. The following will add a dependency to the full library:
4343
4444``` gradle
4545compile 'com.google.android.exoplayer:exoplayer:r2.X.X'
@@ -56,8 +56,8 @@ compile 'com.google.android.exoplayer:exoplayer-dash:r2.X.X'
5656compile 'com.google.android.exoplayer:exoplayer-ui:r2.X.X'
5757```
5858
59- The available modules are listed below. Adding a dependency to the full
60- ExoPlayer library is equivalent to adding dependencies on all of the modules
59+ The available library modules are listed below. Adding a dependency to the full
60+ library is equivalent to adding dependencies on all of the library modules
6161individually.
6262
6363* ` exoplayer-core ` : Core functionality (required).
@@ -66,11 +66,16 @@ individually.
6666* ` exoplayer-smoothstreaming ` : Support for SmoothStreaming content.
6767* ` exoplayer-ui ` : UI components and resources for use with ExoPlayer.
6868
69- For more details, see the project on [ Bintray] [ ] . For information about the
70- latest versions, see the [ Release notes] [ ] .
69+ In addition to library modules, ExoPlayer has multiple extension modules that
70+ depend on external libraries to provide additional functionality. Some
71+ extensions are available from JCenter, whereas others must be built manaully.
72+ Browse the [ extensions directory] and their individual READMEs for details.
7173
74+ More information on the library and extension modules that are available from
75+ JCenter can be found on [ Bintray] [ ] .
76+
77+ [ extensions directory] [ ] : https://github.com/google/ExoPlayer/tree/release-v2/extensions/
7278[ Bintray ] : https://bintray.com/google/exoplayer
73- [ Release notes ] : https://github.com/google/ExoPlayer/blob/release-v2/RELEASENOTES.md
7479
7580### Locally ###
7681
@@ -109,15 +114,9 @@ compile project(':exoplayer-library-ui')
109114
110115#### Project branches ####
111116
112- * The project has ` dev-vX ` and ` release-vX ` branches, where ` X ` is the major
113- version number.
114- * Most development work happens on the ` dev-vX ` branch with the highest major
115- version number. Pull requests should normally be made to this branch.
116- * Bug fixes may be submitted to older ` dev-vX ` branches. When doing this, the
117- same (or an equivalent) fix should also be submitted to all subsequent
118- ` dev-vX ` branches.
119- * A ` release-vX ` branch holds the most recent stable release for major version
120- ` X ` .
117+ * Development work happens on the ` dev-v2 ` branch. Pull requests should
118+ normally be made to this branch.
119+ * The ` release-v2 ` branch holds the most recent release.
121120
122121#### Using Android Studio ####
123122
0 commit comments