Check for presence of project-wide gradle configuration properties #2047
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As recommended by the Android Developer Document Gradle Tips & Tricks (See "Configure project-wide properties"), if the hosting application defines the following properties in their root
build.gradle
, peer modules (likereact-native-maps
) can align its dependencies as requested:📂
android/build.gradle
📂
android/app/build.gradle
This provides a much better mechanism for aligning
play-services
version than all the nasty business ofexclude group
:Many other modules are beginning to implement this project-wide configuration properties mechansism, eg:
react-native-background-geolocation
react-native-background-fetch
react-native-device-info
react-native-firebase