[ann] Custom Proguard JAR now required; Android SDK moved to toolchain tasks in automation

--089e082c4eb836d6a0055b5d293d
Content-Type: text/plain; charset="UTF-8"

Hi folks,

I just landed a mess of code that makes the Fennec build require a custom
Proguard JAR [1] (i.e., not one in the Android SDK) and that migrates the
Android SDK fetching from tooltool to the new shiny toolchain tasks [2].
The Android Gradle dependency fetching will migrate soon too [3].

Assuming this sticks, *you will need to fetch this new Proguard JAR*.  You
can do so with

|./mach artifact toolchain -v --from-build proguard-jar|

If that doesn't work, it may be that the JAR hasn't made it's way into the
toolchain indexes yet.  Try

|env MOZ_SCM_LEVEL=1 ./mach artifact toolchain -v --from-build proguard-jar|

The Android SDK toolchain task means that you can bump
http://searchfox.org/mozilla-central/source/python/mozboot/mozboot/android-packages.txt
in a try build and automatically get an updated SDK.

The Android Gradle dependency fetching task will soon mean that you can
bump **/*.gradle and get updated Gradle dependencies in your Gradle build.

This is all in service of transitioning to Gradle in Fennec 58 [4].

Please let me and Max Liu, my partner in crime, know about fallout.  Let's
hope it all sticks!

Yours,
Nick

[1] https://bugzilla.mozilla.org/show_bug.cgi?id=1352599
[2] https://bugzilla.mozilla.org/show_bug.cgi?id=1405412
[3] https://bugzilla.mozilla.org/show_bug.cgi?id=1405413
[4] https://bugzilla.mozilla.org/show_bug.cgi?id=gradle-automation-v1

--089e082c4eb836d6a0055b5d293d
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi folks,</div><div><br></div><div>I just landed a me=
ss of code that makes the Fennec build require a custom Proguard JAR [1] (i=
..e., not one in the Android SDK) and that migrates the Android SDK fetching=
 from tooltool to the new shiny toolchain tasks [2].=C2=A0 The Android Grad=
le dependency fetching will migrate soon too [3].</div><div><br></div><div>=
Assuming this sticks, *you will need to fetch this new Proguard JAR*.=C2=A0=
 You can do so with</div><div><br></div><div>|./mach artifact toolchain -v =
--from-build proguard-jar|</div><div><br></div><div>If that doesn&#39;t wor=
k, it may be that the JAR hasn&#39;t made it&#39;s way into the toolchain i=
ndexes yet.=C2=A0 Try</div><div><br></div><div>|env MOZ_SCM_LEVEL=3D1 ./mac=
h artifact toolchain -v --from-build proguard-jar|</div><div><br></div><div=
>The Android SDK toolchain task means that you can bump <a href=3D"http://s=
earchfox.org/mozilla-central/source/python/mozboot/mozboot/android-packages=
..txt">http://searchfox.org/mozilla-central/source/python/mozboot/mozboot/an=
droid-packages.txt</a> in a try build and automatically get an updated SDK.=
</div><div><br></div><div>The Android Gradle dependency fetching task will =
soon mean that you can bump **/*.gradle and get updated Gradle dependencies=
 in your Gradle build.</div><div><br></div><div>This is all in service of t=
ransitioning to Gradle in Fennec 58 [4].</div><div><br></div><div>Please le=
t me and Max Liu, my partner in crime, know about fallout.=C2=A0 Let&#39;s =
hope it all sticks!</div><div><br></div><div>Yours,</div><div>Nick</div><di=
v><br></div><div>[1] <a href=3D"https://bugzilla.mozilla.org/show_bug.cgi?i=
d=3D1352599">https://bugzilla.mozilla.org/show_bug.cgi?id=3D1352599</a><br>=
</div><div>[2] <a href=3D"https://bugzilla.mozilla.org/show_bug.cgi?id=3D14=
05412">https://bugzilla.mozilla.org/show_bug.cgi?id=3D1405412</a><br></div>=
<div>[3] <a href=3D"https://bugzilla.mozilla.org/show_bug.cgi?id=3D1405413"=
>https://bugzilla.mozilla.org/show_bug.cgi?id=3D1405413</a><br></div><div>[=
4] <a href=3D"https://bugzilla.mozilla.org/show_bug.cgi?id=3Dgradle-automat=
ion-v1">https://bugzilla.mozilla.org/show_bug.cgi?id=3Dgradle-automation-v1=
</a><br></div></div>

--089e082c4eb836d6a0055b5d293d--
0
Nicholas
10/12/2017 5:49:24 PM
mozilla.dev.builds 1679 articles. 0 followers. Post Follow

0 Replies
26 Views

Similar Articles

[PageSpeed] 27

Reply: