Closed Bug 1001713 Opened 10 years ago Closed 8 years ago

Configure ProGuard to strip new Assert classes and calls from release builds

Categories

(Firefox Build System :: Android Studio and Gradle Integration, defect)

All
Android
defect
Not set
normal

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
Blocks: 1001063
Blocks: 1042363
No longer blocks: fatfennec
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
As of Bug 1240579, this is not needed.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INVALID
Product: Firefox for Android → Firefox Build System
You need to log in before you can comment on or make changes to this bug.