教程 http://blog.csdn.net/android_panda/article/details/18604121
配置文件 http://www.cnblogs.com/0616--ataozhijia/p/3723967.html
参考 http://blog.sina.com.cn/s/blog_ac843e330102vrae.html
代码混淆详解 http://blog.csdn.net/z157794218/article/details/40039785/
排除混淆工具的问题 https://sourceforge.net/projects/proguard/files/proguard/5.3/proguard5.3.3.zip/download
java.lang.VerifyError。这个异常只会在类加载过程中的“校验”步骤抛出，意思是该Class文件的内容未能通过校验器的校验。换句话说，抛出这个异常的时候，它所说的类尚未完成加载，其中的方法自然也不可能被执行
Java 7 introduced stricter verification and changed the class format a bit—to contain a stack map used to verify that code is correct. The exception you see means that some method doesn't have a valid stack map.
Java version or bytecode instrumentation could both be to blame. Usually this means that a library used by the application generates invalid bytecode that doesn't pass the stricter verification. So nothing else than reporting it as a bug to the library can be done by the developer.
As a workaround you can add -noverify to the JVM arguments in order to disable verification. In Java 7 it was also possible to use -XX:-UseSplitVerifier to use the less strict verification method, but that option was removed in Java 8.
成功运行