proguard

after Proguard obfuscation i get the following error : Unexpected exception parsing XML document from ServletContext resource [/WEB-INF/applicationContext.xml]; nested exception is java.lang.IllegalStateException: Annotation-specified bean name 'a' for bean class [com.company.project.b.a.a.a] conflicts with existing, non-compatible bean definition of same name and class [com.company.project.a.a] i'm using annotation based spring configuration , how can i avoid having two classes with the same name using Proguard because Spring doesn't allow two beans to have the same name. I'm not sure if this

I have an Interface class A and in the Class A i have another Interface B I am trying to proguard the Package and when i build it in gradle I getting The below error symbol: class B location: interface A ../Progaurd/android/trunk/sample/module-c/src/main/java/com/c/db/C.java:24: error: cannot find symbol public class C implements B The actual class is as follows public interface A{ public interface B{ ... } } I have tried with the below lines in proguard-project.txt file -keep class * implements com.sample.manager.storage.A.B Please help me.... -keep public interface com.sample.manager.storage

I successfully processed my jar and apk. Then, want to verify if is it truly hard to reverse engineer or truly did the obfuscation. I am thinking to try to reverse engineer it by myself to see what I did. But don't know how to do it. For manual reverse engineering, you can try dex2jar and then Java Decompiler . I assume you have a set of tests (unit/functionality). Run them against the obfuscated jar file. They should pass as if you had the original program. 来源： https://stackoverflow.com/questions/7478809/android-java-proguard-how-to-verify-if-my-jar-different-jar-project-apk-ar

I'm trying to obfuscate my package names including that one of my used libraries. I use this build config in my gradle file: buildTypes { debug { versionNameSuffix "-Development" debuggable true runProguard true proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro' } #... This is my proguard file: # Butterknife -dontwarn butterknife.internal.** -keep class **$$ViewInjector { *; } -keepnames class * { @butterknife.InjectView *;} # OrmLite uses reflection -keepclassmembers class com.j256.** { *; } -keep class my.package.name.database.** { *; } -keep class com.j256.**

I'm trying to get Proguard to obfuscate a simple .war file. According to the docs Proguard handles .war files, but when I try I get this: Warning: class [WEB-INF/classes/com/corp/gr/t2b/T2BChannel.class] unexpectedly contains class [com.corp.gr.t2b.T2BChannel] The docs mention something about Proguard not liking .war files with classes in the WEB-INF/classes directory. So I put all the .class files in their own .jar file in WEB-INF/lib. Then Proguard complains that it cannot find any of the JavaEE 6 classes, even though I've given it the javaee.jar file with -libraryjars C:/bin/glassfish-3.0.1

I'm configuring Proguard for an app that uses 3rd party libraries. Is it "best practice" (in order to avoid future hard-to-find bugs) to include the line: -keep class 3rd_party_lib_name.** {*;} for every single 3rd party open source library that doesn't have specific Proguard instructions from its developer? Also, a related question: is there a general guideline for which cases I should use -keep class and in which cases i should use -keep public class many thanks ben75 The major problem with proguard and code obfuscation in general is that classname, methods and fields name are modified. ( i