Debian Codegraph @

tests/inputs/proguard-project-app.pro

raw
1 # https://raw.githubusercontent.com/krschultz/android-proguard-snippets/master/examples/proguard-project-app.pro
2 # The simpliest strategy is to not run proguard against your project's own code.
3 # This doesn't provide the benefits of optimization & obfuscation against your
4 # project, but will still strip the libraries. The advantage is that your app will
5 # work without any subsequent effort. If you choose this strategy, the proguard
6 # configuration for the project is simply the line below.
7
8 -keep class com.yourpackage.app.** { *; }
9
10 # The more involved strategy is to specifically provide rules to keep portions of your
11 # app's codebase unmodified while allowing proguard to optimize the rest.
12
13 # The first decision is whether or not you want to obfuscate your code. This provides no
14 # performance benefit but makes it harder for other people to read your source code.
15 # Unfortunately obfuscation can cause issues for code that uses reflection or a few other
16 # techniques. The default is to obfuscate.
17
18 -dontobfuscate
19
20 # Additionally you will need to keep specific classes. A common use case is keeping all
21 # of the models that are JSON parsed using something like Jackson.
22
23 -keep class com.yourpackage.app.model.User { *; }
24