Issue 264: Use proguard to reduce size of Guice
http://code.google.com/p/google-guice/issues/detail?id=264

New issue report by mcculls:
The current Guice library built from trunk is ~900k because JarJar only
works at the class level. It doesn't trim classes with lots of static
methods (as in Google Collections) and this leads to many unnecessary
classes getting left in. Extending JarJar to trim static methods looks
non-trivial.

Switching over to just use ProGuard is also not an option, because it
cannot seem to handle the CGLIB code properly (it ends up obfuscating
classes and members too much, which somehow breaks CGLIB).

The only reasonable option I've found is to apply ProGuard first to remove
unused static collection methods and use JarJar to repackage CGLIB, etc.

With the attached patch, the Guice jar drops to ~600k

[also attached ProGuard 4.3 beta 1 from http://proguard.sourceforge.net/]

Attachments:
        GUICE_PROGUARD_PATCH.txt  2.1 KB
        proguard.jar  617 KB


Issue attributes:
        Status: New
        Owner: ----
        Labels: Type-Defect Priority-Medium

-- 
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"google-guice-dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/google-guice-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to