So actually yes it runs proguard which is normal. This is not the proguard that you configure in the build type in order to shrink/obfuscate. This is the proguard action that we run to compute the list of classes to go in the main dex file for legacy multi-dex. It runs with different set of properties.
If you have enabled proguard you would actually have seen 2 runs of proguard. This run is tied to the multidex flag and having minSdkVersion < 21. On Sat, Sep 19, 2015 at 12:53 PM, Tomáš Procházka <[email protected] > wrote: > I found the same problem. Is also very interesting that it run Proguard > for debug build. > > Dne pátek 18. září 2015 3:31:51 UTC+2 Xavier Ducrohet napsal(a): >> >> thanks for the report, we'll get this fixed. >> >> On Thu, Sep 17, 2015 at 9:32 AM, Ariel Cattan <[email protected]> wrote: >> >>> Hey guys, >>> >>> I found another issue with the Android Gradle Plugin version 1.4.0-beta2 >>> which uses the Transform API. >>> Apparently when building a project with multidex enabled, Proguard is >>> automatically triggered (without requesting it, in the debug build-type), >>> and generates lots of warnings on a project that normally builds fine with >>> proguard. >>> >>> >>> -- > 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. > -- Xavier Ducrohet Android SDK Tech Lead Google Inc. http://developer.android.com | http://tools.android.com Please do not send me questions directly. Thanks! -- 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.
