Make apks build from a single ant .xml template

build/android/ant/common.xml

 <?xml version="1.0" encoding="UTF-8"?>
 <!--
   Copyright (c) 2012 The Chromium Authors. All rights reserved.
   Use of this source code is governed by a BSD-style license that can be
   found in the LICENSE file.
 -->
 <project name="chrome_common_defines">
   <!-- Common build properties for Chrome for android. -->
 
   <!--
+    TODO(cjhopman): Remove this when all ant calls properly define
+    CONFIGURATION_NAME.
+  -->
+  <property name="CONFIGURATION_NAME" value="Debug"/>
+
+  <!--
+    Convert the buildtype to lowercase. E.g Debug -> debug,
+    Release -> release.
+  -->
+  <script language="javascript">
+    project.setProperty("configuration.name",

[shashi, 2012/09/21 01:53:55]

Where is configuration.name used?

[cjhopman, 2012/09/28 01:14:25]

This was introduced a long time ago towards supporting debug and release. I have
a simpler way of handling this that I'll add soon (as we begin seriously
considering support of both configurations) and so I've removed this.

+                        project.getProperty("CONFIGURATION_NAME").toLowerCase())
+  </script>
+
+  <!--
     Macro for checking that a property is correctly set. Performs checks for:
     1. Property is set and not null.
     2. String value of property does not contains any '$' signs.
   -->
   <macrodef name="check-property-value">
     <attribute name="property"/>
     <sequential>
       <fail message ="Property @{property} is not set.">
         <condition>
           <or>
@@ skipping 60 matching lines @@
        build/android/pylib/constants.py
   -->
   <!-- Common directory for chromium_*.jars. -->
   <property-location name="lib.java.dir" location="${PRODUCT_DIR}/lib.java"/>
   <!-- Common directory for test jars. -->
   <property-location name="test.lib.java.dir"
     location="${PRODUCT_DIR}/test.lib.java"/>
   <!-- Common directory for apks. -->
   <property-location name="apks.dir" location="${PRODUCT_DIR}/apks"/>
 </project>