Proguard User Manual: ProGuard requires the library jars (or wars, ears, zips, or directories) of the input jars to be specified. It can then reconstruct class hierarchies and other class dependencies, which are necessary for proper shrinking, optimization, and obfuscation. The library jars themselves always remain unchanged. You should still put them in the class path of your final application.
--- Torsten Curdt <[EMAIL PROTECTED]> wrote: > On 8/5/06, Anil Philip <[EMAIL PROTECTED]> > wrote: > > You mentioned "It's not as sophisticated as > proguard > > that does even remove dead code inside classes." > > However Proguard leaves libraries alone. Does your > > minijar operate on libraries? eg. > commons-net-1.4.jar > > Or would I have to build the jar from the original > > source? > > Not sure what you mean by "However Proguard leaves > libraries alone" > ...but minijar does work on the jar - no need for > the sources. It does > remove unused classes but not methods like proguard > does. I personally > found the gain of removing methods too small to > justify the effort. > (did a few comparisons) > > HTH > -- > Torsten > > --------------------------------------------------------------------- > To unsubscribe, e-mail: > [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] > > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
