| 1234567891011121314151617181920212223242526272829303132 |
- ### Updating Gradle Dependencies
- If additional Android dependencies are required by the project's build, then
- the Gradle build will fail due to missing dependencies. To find out what the
- missing dependencies are, comment out the following line in the project's build
- file:
- export GRADLE_MAVEN_REPOSITORIES="file://$rootdir/[% c('input_files_by_name/gradle-dependencies') %]"
- then allow network access during the build by setting
- var/container/disable_network/build to 0 in rbm.conf, and rerun the build.
- Dependent artifacts will show up as downloads in the logs. You can pull out
- these dependencies into a list with the following command (replacing
- "firefox-android-armv7.log" with the build log file name of the actual project):
- `cat logs/firefox-android-armv7.log | grep "Download http" | sed "s/^.*Download //g" > download-urls.txt`
- You will then need to add the new dependency URLs and SHA-256 values into the
- projects/$project/gradle-dependencies-list.txt file. The format of this file is
- pipe delimited
- sha256sum | url
- Finally, in the project's config file increment the
- var/gradle_dependencies_version and make sure to restore the project's build
- file back to original.
- It may also be the case that you wish to clean up old versions of the artifacts.
- For this you will need to run the build with a
- gradle-dependencies-list.txt file containing only the headers. Make sure to also
- comment the GRADLE_MAVEN_REPOSITORIES line from the project's build file. You
- can now proceed to reconstruct the list as given above.
|
