You could also use a resolution strategy for the classpath configuration and force the desired version. That would prevent the need for checking in a jar.
On Thu, Aug 11, 2016, 6:10 AM Kirill Rakhman <[email protected]> wrote: > Turns out, that's pretty easy. Place the ProGuard jar in your project and > modify the top-level build.gradle as follows: > > buildscript { > repositories { > jcenter() > } > dependencies { > classpath 'com.android.tools.build:gradle:2.2.0-beta1' > classpath files('proguard5.3beta.jar') > } > > configurations.classpath.exclude group: 'net.sf.proguard' > } > > > > > Am Mittwoch, 10. August 2016 18:08:07 UTC+2 schrieb Kirill Rakhman: >> >> I'm looking for a way to make the Gradle build process use ProGuard 5.3 >> Beta instead of the bundled version 5.2. The reason is a specific bug ( >> https://sourceforge.net/p/proguard/bugs/617/) in combination with using >> Kotlin (https://youtrack.jetbrains.com/issue/KT-12346). >> >> I would accept a hacky solution as the problem will go away when 5.3 is >> bundled with the plugin anyway. >> >> Thanks in advance for any suggestions. >> > -- > You received this message because you are subscribed to the Google Groups > "adt-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "adt-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
