Yes, this is currently the case due to an internal limitation of Gradle. I'm hoping to get this improved in the future.
On Fri, Jul 11, 2014 at 10:58 AM, Joe Blubaugh <[email protected]> wrote: > Hello, > > I have a multi-project setup with the following structure: > > + > |-app > |-lib1 > |-lib2 > > And for the app I have two flavors: > > android { > ... > productFlavors { > vanilla > chocolate > } > } > > dependencies { > compile 'com.android.support:support-v4:20.+' > vanillaCompile project(':lib1') > chocolateCompile project(':lib2') > } > > what I am finding when running assembleVanillaDebug, > assembleChocolateDebug is that these tasks both depend on bundling both > libraries: > > > app $ ../gradlew tasks > > assembleVanillaDebug - Assembles the Debug build for flavor Vanilla > [:lib1:bundleRelease, :lib2:bundleRelease] > > Does anyone know why this is the case? This means that if lib2 is broken I > can't build an APK that doesn't depend on lib2. > > Thanks, > > Joe Blubaugh > > -- > 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.
