Add rules, such as preserving class and method names, according to your needs. This file will contain the ProGuard rules specific to your application. ProguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'įor Maven, add the following to your `pom.xml` file under the `plugins` block:Ĭom.github.wvengen proguard-maven-plugin 2.2.0 package proguard 7.1.0 true nfĬreate a new file named `proguard-rules.pro` (Gradle) or `nf` (Maven) in your project’s root directory. Implementation 'com.guardsquare:proguard-gradle:7.1.0'Īnd under the `buildTypes` block, add the following: If you’re using a build system like Gradle or Maven, you can add ProGuard as a plugin to your build configuration.įor Gradle, add the following to your app-level `adle` file under the `dependencies` block: Extract the downloaded archive to a folder on your computer. Visit ProGuard’s official website at and download the latest version. Here’s a step-by-step guide to using a popular Java obfuscator, ProGuard: It’s commonly used to protect intellectual property within your code, especially for commercial software. Programming GuideĪn obfuscator in Java is a tool that scrambles your source code to make it harder for others to understand and reverse-engineer. Learn how to download and configure the build system for Gradle or Maven, create a configuration file with rules specific to your application, and run the obfuscation on your code in release mode. ProGuard's Gson rewriting requires a lot of known behavior and assumptions that could break (if Gson weren't abandonware).This blog post provides a step-by-step guide to using ProGuard, a popular Java obfuscator.
However, for AndroidX's Pair it will unwrap it because the implementation is part of the code being compiled and thus it can see constructor arguments become field values and then field reads in the same method and skip the allocation. For example, R8 will not unbox use of because that class belongs to the framework and it cannot see the implementation to know the constructor arguments always end up on the fields. Soundness, in this case, means not having any pre-baked knowledge of a library to rewrite its usages including assumptions that are not inferred.
See weekly downloads, latest versions and community scores in the Debricked Open Source Select. ProGuard seems much more willing to meet developers where they are and optimize real world patterns even if they are otherwise unsound. Get an overview of maven: com.guardsquare:proguard-gradle. The R8 team tends to focus on optimizations that are sound (or reasonably sound) at the expense of leaving some optimizations on the table. For example, it has a bonkers feature where it will rewrite Gson usage to use less reflection.
ProGuard has many features that R8 does not provide.
0 kommentar(er)
