| commit | 2a349ed89c34f73e0e785473fdaf62de9f1e08bc | |
| author | Grisha Kruglov <gkruglov@mozilla.com> | |
| Fri, 4 Oct 2019 23:01:12 +0000 (4 16:01 -0700) | ||
| committer | Grisha Kruglov <grigory@kruglov.ca> | |
| Mon, 7 Oct 2019 21:13:33 +0000 (7 14:13 -0700) | ||
| tree | 12c8de13f06a32e0e89f58d3484f29698826a9c5 | treesnapshot (tar.gz zip) |
| parent | 0eeea7695f7179f926a50f57fb63eeda97069f6f | commitdiff |
[fenix] Closes https://github.com/mozilla-mobile/fenix/issues/1022: Auto-publication workflow for android-component
This patch enabled support for an auto-publication workflow for android-components.
It automates a common pattern seen in local development:
Old way:
- after every change in a-c, publish it locally with a unique version (bumping it manually)
- manually modify Fenix to consume a custom version of a-c from a mavenLocal repository
New way:
- set a flag in fenix's local.properties to enable auto-publication
- run Fenix builds after making changes to a-c. Changes in a-c will be automatically picked up.
Note that no changes are necessary to any Fenix files other than a single flag in local.properties.
Manually bumping android-components version is also not necessary.
This patch enabled support for an auto-publication workflow for android-components.
It automates a common pattern seen in local development:
Old way:
- after every change in a-c, publish it locally with a unique version (bumping it manually)
- manually modify Fenix to consume a custom version of a-c from a mavenLocal repository
New way:
- set a flag in fenix's local.properties to enable auto-publication
- run Fenix builds after making changes to a-c. Changes in a-c will be automatically picked up.
Note that no changes are necessary to any Fenix files other than a single flag in local.properties.
Manually bumping android-components version is also not necessary.
| mobile/android/fenix/app/build.gradle | diffblobblamehistory | |
| mobile/android/fenix/settings.gradle | diffblobblamehistory |