Sure. Which spread the code everywhere and I have to remember to change it in every point if I need to. I also miss the chance to provide a default value.
I appreciate you are helping me, but what I really need is more flexibility on the gradle side so that I can provide all my setting there, in a single place, easily work with default cases, .... On Friday, November 14, 2014 4:58:45 PM UTC+1, Avram Lyon wrote: > > On Fri, Nov 14, 2014 at 1:42 AM, Daniele Segato <[email protected] > <javascript:>> wrote: > >> That's not the same. >> >> I know I can do the switch Java side but it's a completely different >> thing. >> >> If I use that to set API Keys etc. I don't want ALL OF THEM to be in the >> Java file. That will be compiled and packaged with the APK. >> >> I want to set it in the build file and have only 1 of the value in the >> APK. The one needed by that APK. >> > > In that case you can provide flavor-specific Constants.java files in the > flavor-specific source sets. So long as you ensure that every flavor > combination has such a file present, it'll work. Such an approach won't > support merging of constant definitions, of course. > -- 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.
