I think we'll never remove those values from the manifest because this is how they end up being packaged anyway. We also need to be able to open older projects that don't have a build.gradle file.
The ability to set this values from build.gradle bring a lot of flexibility but it does bring a confusion when someone changes a value in the wrong place. I think we already have lint checks in place that will let you know if you have a value defined in both places. On Thu, May 15, 2014 at 11:52 AM, Andrew McKinlay <[email protected] > wrote: > Some properties in the manifest.xml can also be specified in build.gradle. > What is the future of this dual origin of truth? Will build.gradle > eventually replace the manifest file? > > -- > 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.
