This is not really possible at the moment. You'd have to include common but exclude whatever it depends on, and then have your 2 flavors manually include LibA and LibB.
However, if common overrides some resources from libA and libB it might not work. On Thu, Jun 26, 2014 at 8:24 AM, Valerio Santinelli <[email protected]> wrote: > Hello everybody, > > I've got a project that is made up of many modules (libraries) and a root > project which is the actual app. > The original author made everything in Eclipse and I converted it to > Android Studio and Gradle when I had to work on it. > You can read how the project is structured on StackOverflow, where I went > into details: > http://stackoverflow.com/questions/24410995/conditional-dependencies-with-gradle-is-it-possible > > I haven't yet found a solution for my problem. > What I want to achieve is have the main project include a library and that > library should include another library based on the flavor that I'm > building so that I either end up having: > > - Project M + Library Common + Library A > - Project M + Library Common + Library B > > where Library A and Library B are basically two modules that contain > different resources. > > Is there anyone who could help me find the solution? > > If you need further info just let me know here or on the post at SO. > Thanks! > > Valerio > > -- > 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.
