I'm noticing in some builds on Jenkins (but never in local builds), that the proguardFiles specified in a custom buildType are appended out of order.
Can anyone think of a reason that this could happen? In the affected script, there are three buildTypes (debug, release, and dist), and there are two dimensions of flavors. However, the proguardFiles are only specified in buildTypes, and it is only the dist (custom) type where the files are sometimes added out of order. By out of order, I mean that the getDefaultProguardFile( 'proguard-android-optimize.txt') listed first is added last. And because its optimizations rule ends in a negated item, the resulting optimizations *enables* all unmatched optimization names. To workaround, I added ",!**" to the end of the last proguard file's optimizations (in case its items were erroneously appended first). -- 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.
