Closed
Bug 1001713
Opened 11 years ago
Closed 9 years ago
Configure ProGuard to strip new Assert classes and calls from release builds
Categories
(Firefox Build System :: Android Studio and Gradle Integration, defect)
Firefox Build System
Android Studio and Gradle Integration
All
Android
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: nalexander, Unassigned)
References
(Blocks 1 open bug)
Details
Further to ckitching's analysis at [1],
We should configure Proguard to strip the new Assert class landed in Bug 1001063. I'm a little confused as to how the org.mozilla.gecko.Assert class in that ticket avoids conflicting with org.mozilla.gecko.Assert from Robocop, but I'm sure it's clear once one investigates.
[1] https://mail.mozilla.org/pipermail/mobile-firefox-dev/2014-April/000628.html
[2] https://bugzilla.mozilla.org/show_bug.cgi?id=1001063
Updated•10 years ago
|
Summary: [build] Configure Proguard to strip new Assert classes and calls from release builds → Configure ProGuard to strip new Assert classes and calls from release builds
Reporter | ||
Comment 1•9 years ago
|
||
As of Bug 1240579, this is not needed.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INVALID
Updated•5 years ago
|
Product: Firefox for Android → Firefox Build System
You need to log in
before you can comment on or make changes to this bug.
Description
•