I am hoping that one of these days someone ends up forking Proguard
altogether (this is something the JarJar authors might want to
consider). I like Eric well enough but he seems unwilling to give
anyone else commit rights. I am uncomfortable relying on a single
developer projects and of course he is severely overloaded with work
so development goes very slowly.
There are plenty of features I'd like to see added on the obfuscation
and ease-of-use front, much less so on the optimization front which he
seems to be focused on for the past couple of years. Just my 2
cents ;)
Gili
On Oct 27, 1:13 pm, "Stuart McCulloch" <[EMAIL PROTECTED]> wrote:
> 2008/10/28 Gili <[EMAIL PROTECTED]>
>
>
>
> > I'm thinking that maybe all you need is a Proguard configuration
> > (above and more below) and some third-party (such as JarJar) to move
> > some packages around and you're done. You'd run Proguard with
> > shrinking enabled, obfuscation disabled, and look into whether
> > optimization should be enabled or not.
>
> exactly - that's basically the patch I attached to issue 264 (ProGuard then
> JarJar)
>
>
>
> > Here is the second part of the Proguard configuration you will need to
> > prevent Guice-specific classes from being removed:
>
> > # Referenced by com.google.inject.AbstractModule
> > -keep class com.google.inject.Binder
> > {
> > *;
> > }
>
> > # Keep any constructors annotated with @Inject
> > -keepclassmembers class *
> > {
> > [EMAIL PROTECTED] <init>(...);
> > }
>
> > At least, this is what I used for Guice 1.0
>
> --
> Cheers, Stuart
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"google-guice" 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?hl=en
-~----------~----~----~----~------~----~------~--~---
