This is working as intended (it worked like this in Ant/ADT as well). We need to add diagnostic tools to let you devs understand exactly what's going on.
On Fri, Aug 8, 2014 at 4:24 PM, James Wald <[email protected]> wrote: > I have a multi-project build that is structured like this: > > root/ > app/ > build.gradle -> dependencies: libA, libB > libA/ > src/main/res > styles.xml -> @style/AppTheme > build.gradle > libB/ > src/main/res > styles.xml -> @style/AppTheme > build.gradle > > When declaring app's dependencies, these produce different resources after > the merge process: > > dependencies { > compile project(':libA') > compile project(':libB') > } > > dependencies { > compile project(':libB') > compile project(':libA') > } > > The library that is declared first in the dependencies block wins and the > other library's @style/AppTheme resource is ignored. Since the libraries > both declare @style/AppTheme and do not depend on each other, I was > expecting the build to fail with a resource merging conflict. I'm wondering > whether this is a bug or working as intended? > > -- > 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.
