title: best practice for flavored build variants with gradle in android studio
body: <p>I have an App that is produced for different brands.  Now I have two flavors, brand1 and brand2. The difference between brand1 and brand2 are only the resource files.</p>
  
  <p>First I assumed I could set all shared data into my main path and the differences into the flavored path. But in this scenario my build failed, because resources in my main path are missing.</p>
  
  <p>I would go on like this: set all resource differences between the brands in the main path as dummy data. The merge will do the rest for me. </p>
  
  <p>In iOS I can set a build path for each build target. 
  Is something like this possible with flavors? Or what is the best practice in this situation?</p>
  
  <p><strong>[EDIT 2013 08 07]</strong> </p>
  
  <p>The problem in my case was that I created the app in eclipse and exported it to android studio. 
  <a href="https://groups.google.com/forum/#!searchin/adt-dev/best%2420practice/adt-dev/Gn_Nw_MVn1s/EJcxZzOfAeYJ" rel="nofollow">Here</a> the problem and solution is described more precisely. </p>