-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Dependency substitution for android-components #1022
Comments
We should be mostly unblocked here. A-C needs to move to AndroidX but IIUC nothing is in the way of that. |
@grigoryk is this still waiting on anything? |
I think this is covered by using
|
Here are pretty precise instructions on what needs to happen here: mozilla-mobile/reference-browser#365 (comment) Nothing should be blocking this work, just needs to be tested. |
We've had a very traumatic past few weeks trying to do tight iterations across three levels of the stack (a-s -> a-c -> fenix), and not having this done yet has been such a pain. So let's bump this up in priority. |
Actually, I don't know what Fenix labels really mean, so I'll re-add it. In any case, this will be done as part of an a-c sprint. |
@grigoryk: @jonalmeida and I both tried that in RB (earlier draft: mozilla-mobile/reference-browser#815) and the result has been horrible. Mostly because:
|
…ponent 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.
…ponent 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.
@pocmo i've ran into the same behaviour, and couldn't work around it. So instead went for automating a local publication workflow. |
I think this does not work for windows, since you have to call "gradlew.bat", not "gradle". |
This will allow us to easily develop against a local checkout of
android-components
.Currently blocked on a-c moving to AndroidX (mozilla-mobile/android-components#842). Also, see similar r-b issue: mozilla-mobile/reference-browser#365
┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: