（一）ant介绍
ant是自动化拷贝、编译、发布的构建工具，简单跨平台。
（二）ant使用前奏
1.安装jdk并配合环境变量
2.安装sdk并配合环境变量
3.新版的android sdk已经自带了ant在/eclipse/plugins目录下，如需下载到http://ant.apache.org，新建环境变量ANT_HOME为ant目录，path为%ANT_HOME%/lib
（三）编译发布android项目
1.生成build.xml文件
运行android update project -p xxx （xxx为项目路径）
在项目根目录下自动生成build.xml、local.properties两个文件
build.xml已做基本配置和调用sdk本身自带的build.xml文件，local.properties已设置sdk目录
2.打包项目
新建ant.properties，放入keystore签名信息
key.store=zhangzhongcai.keystore
key.store.password=xxx
key.alias=xxx
key.alias.password=xxx
根目录下放入zhangzhongcai.keystore签名文件
若不指定key.store.password和key.alias.password会在运行过程中要求输入，提高安全性
运行ant release打包
（四）多渠道自动化打包
1.多渠道打包需要修改配置文件，完成渠道信息修改再打包，ant本身没有for命令，修改xml文件也不方便，需要使用第三方扩展包Ant-contrib，从这里可以下载到，下载完在项目中新建lib文件夹放入。
2.新建channel.properties加入渠道信息
<span style="font-size:18px;">market_channels=anzhi,360,baidu</span>
3.修改build.xml支持多渠道自动化打包，有两种方式
(1)添加custom_rules.xml，将自动化打包脚本写入，打包前初始化会调用custom_rules.xml内容
(2)将自动化打包脚本写入build.xml，如下
<?xml version="1.0" encoding="UTF-8"?>
<project name="TestRelease" default="deploy">
<!-- The local.properties file is created and updated by the 'android' tool.
It contains the path to the SDK. It should *NOT* be checked into
Version Control Systems. -->
<property file="local.properties" />
<!-- The ant.properties file can be created by you. It is only edited by the
'android' tool to add properties to it.
This is the place to change some Ant specific build properties.
Here are some properties you may want to change/update:
source.dir
The name of the source directory. Default is 'src'.
out.dir
The name of the output directory. Default is 'bin'.
For other overridable properties, look at the beginning of the rules
files in the SDK, at tools/ant/build.xml
Properties related to the SDK location or the project target should
be updated using the 'android' tool with the 'update' action.
This file is an integral part of the build system for your
application and should be checked into Version Control Systems.
-->
<property file="ant.properties" />
<property file="channel.properties" />
<!-- if sdk.dir was not set from one of the property file, then
get it from the ANDROID_HOME env var.
This must be done before we load project.properties since
the proguard config can use sdk.dir -->
<property environment="env" />
<condition property="sdk.dir" value="${env.ANDROID_HOME}">
<isset property="env.ANDROID_HOME" />
</condition>
<!-- The project.properties file is created and updated by the 'android'
tool, as well as ADT.
This contains project specific properties such as project target, and library
dependencies. Lower level build properties are stored in ant.properties
(or in .classpath for Eclipse projects).
This file is an integral part of the build system for your
application and should be checked into Version Control Systems. -->
<loadproperties srcFile="project.properties" />
<!-- quick check on sdk.dir -->
<fail
message="sdk.dir is missing. Make sure to generate local.properties using 'android update project' or to inject it through the ANDROID_HOME environment variable."
unless="sdk.dir"
/>
<!--
Import per project custom build rules if present at the root of the project.
This is the place to put custom intermediary targets such as:
-pre-build
-pre-compile
-post-compile (This is typically used for code obfuscation.
Compiled code location: ${out.classes.absolute.dir}
If this is not done in place, override ${out.dex.input.absolute.dir})
-post-package
-post-build
-pre-clean
-->
<import file="custom_rules.xml" optional="true" />
<!-- Import the actual build file.
To customize existing targets, there are two options:
- Customize only one target:
- copy/paste the target into this file, *before* the
<import> task.
- customize it to your needs.
- Customize the whole content of build.xml
- copy/paste the content of the rules files (minus the top node)
into this file, replacing the <import> task.
- customize to your needs.
***********************
****** IMPORTANT ******
***********************
In all cases you must update the value of version-tag below to read 'custom' instead of an integer,
in order to avoid having your file be overridden by tools such as "android update project"
-->
<!--渠道包打包脚本 ant deploy -->
<!--读入AndroidManifest.xml信息，方便获取软件版本号 -->
<xmlproperty file="AndroidManifest.xml" prefix="appinf" collapseAttributes="true"/>
<taskdef resource="net/sf/antcontrib/antcontrib.properties">
<classpath>
<pathelement location="./lib/ant-contrib-1.0b3.jar"/>
</classpath>
</taskdef>
<target name="deploy">
<foreach target="modify_manifest" list="${market_channels}" param="channel" delimiter=",">
</foreach>
</target>
<target name="modify_manifest">
<replaceregexp flags="g" byline="false">
<!--匹配的内容是 android:value="*****" android:name="UMENG_CHANNEL"-->
<regexp pattern='android:name="UMENG_CHANNEL"
android:value="(.*)"' />
<!--匹配之后将其替换为 android:value="渠道名" android:name="UMENG_CHANNEL" -->
<substitution expression='android:value="${channel}" android:name="UMENG_CHANNEL"' />
<!--正则表达式需要匹配的文件为AndroidManifest.xml -->
<fileset dir="" includes="AndroidManifest.xml" />
</replaceregexp>
<property name="out.release.file" location="${out.absolute.dir}/${ant.project.name}_${channel}.apk" />
<!--打包 -->
<antcall target="release" />
<!--输出渠道包到bin/out目录下 -->
<copy tofile="${out.absolute.dir}/out/${ant.project.name}V${appinf.manifest.android:versionName}_${channel}_release.apk" file="bin/${ant.project.name}-release.apk"/>
</target>
<!-- version-tag: 1 -->
<import file="${sdk.dir}/tools/ant/build.xml" />
</project>
在该目录下运行ant命令，就可以打包出各个渠道的版本到bin/out目录中
原文地址：http://blog.csdn.net/wangpeifeng669/article/details/40343701
