From 1dbee2291be49bf6237571e4260c1a166d5a0e19 Mon Sep 17 00:00:00 2001 From: Christian Sadilek Date: Wed, 2 Nov 2022 11:10:33 -0400 Subject: [PATCH] Closes #27652: Fix A-C auto publish docs in README --- README.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index b2bb54c1c..1729c3e1e 100644 --- a/README.md +++ b/README.md @@ -199,10 +199,12 @@ raptorEnabled If you're making changes to these projects and want to test them in Fenix, auto-publication workflow is the fastest, most reliable way to do that. -In `local.properties`, specify a relative path to your local `android-components` and/or `application-services` checkouts. E.g.: -- `autoPublish.android-components.dir=../android-components` +In `local.properties`, specify a relative path to your local `android-components` and/or `application-services` projects. E.g.: +- `autoPublish.android-components.dir=../firefox-android/android-components` - `autoPublish.application-services.dir=../application-services` +*Note that the Android Components project was already migrated to the new [firefox-android](https://github.com/mozilla-mobile/firefox-android) repository. Therefore, this auto publication workflow won't be neccessary for Android Components once Fenix is integrated in the new repository as well.* + Once these flags are set, your Fenix builds will include any local modifications present in these projects. See a [demo of auto-publication workflow in action](https://www.youtube.com/watch?v=qZKlBzVvQGc).