Sometimes clearing the cache or changing the Proguard version works, but it’s a guessing game, some times it generate the jar file and other times it don’t do anything and just report “up-to-date”.Ĭlasspath("com.guardsquare:proguard-gradle:7.0.I would like to ask if you know a guide or if you know how to use Proguard with Kotlin and Gradle and would like to share your knowledge, I would really appreciate it. I tried to keep running the task to see if that would solve the issue, tried to delete the built shaded jar file, but no, didn’t work out. Thanks, that solved the issue, now my proguard runs, but I got another issue: My proguard task runs, and more often than not the proguard.jar is not generated, it reports in Gradle > Task :proguard UP-TO-DATE even when there’s no proguard.jar file. I’m not in android, why is Proguard requiring it? I cannot even set up the task if I cannot Proguard Gradle imported, I would really appreciate a solution to this missing android-tools dependency. Project : > com.guardsquare:proguard-gradle:7.0.1Ĭlasspath("com.guardsquare:proguard-gradle:7.0.1") The error is the following: Caused by: .ModuleVersionNotFoundException: Could not find :gradle:3.0.0. The documentation only includes guides to Gradle in Android, there is not a single mention of desktop Java in it (which is surprising), not a single Gradle buildscript usage in anything that is not Android. Have you already found the ProGuard Playground? Here you can visualise the ProGuard configuration on your class tree without the need of building the project every single time. On he configuration page you will see the option -obfuscationdictionary explained, which can be used to set up a custom dictionary.Ĭould you please provide the full stack trace? Do you see the error/warning during the build or at runtime? The troubleshooting guide might be able to help you tackle the issue.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |