if module X depends on module A and B, then X uses the release version of A and B.
This is a current limitation of Gradle. https://code.google.com/p/android/issues/detail?id=52962 On Mon, Nov 10, 2014 at 2:15 PM, Magnus Bondesson <[email protected]> wrote: > If I build several of my modules by themselves using assembleDebug, as in > :moduleA:assembleDebug, :moduleB:assembleDebug one release related task is > being called, preReleaseBuild. > 1. Why is that? > > If I however do :moduleX:assembleDebug (where moduleX depends on moduleA > and moduleB) lots of release tasks are called, like > mergeReleaseProguardFiles, packageReleaseAidl etc. > 2. Why is that? > > The reason I care is because it seems that this makes > buildTypes { > release { > runProguard true > > being used which I don't want for debug builds. (don't want to obfuscate) > 3. Is that the reason and if so, how do I stop this from happening? > > Best Regards > Magnus Bondesson > > -- > 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.
