On second thought, it shouldn't matter, as it processes all kept classes anyway...
On Sun, Dec 29, 2013 at 12:48 PM, Perry Nguyen <[email protected]> wrote: > That's actually a very good suggestion, my proguard cache behaves in the > same way (as it is based off of what you did conceptually) > > > On Sun, Dec 29, 2013 at 11:46 AM, James Moore <[email protected]> wrote: > >> On Thu, Dec 26, 2013 at 10:45 PM, Nick Stanchenko >> <[email protected]>wrote: >> >>> P.S. If you use Props[A] or the like for creating actors, you’ll need to >>> add -keep lines for the actor classes as well. I suggest to just use >>> Props(new A) instead. >>> >> >> One other trick is to create a dummy class that contains calls to things >> that you want to keep, and then just tell proguard to keep that one class. >> Sometimes that's easier than mucking around with the Proguard config. Put >> a call to new A in a class that's never instantiated, and you don't have to >> change the way you normally create Akka objects. >> >> >> If you're using my Eclipse plugin, doing it this way will improve your >> cache hits too, since the plugin doesn't know anything about things you've >> kept via proguard config files. >> >> -- >> James Moore >> [email protected] >> http://blog.restphone.com/ >> http://www.linkedin.com/in/jamesmmooreiv >> >> -- >> You received this message because you are subscribed to the Google Groups >> "scala-on-android" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > -- You received this message because you are subscribed to the Google Groups "scala-on-android" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
