android 如何优化ant 批量打包
2024-05-19来源：编辑
1.配置JAVA的环境变量
很多Java程序员由于使用Eclipse不配置Java环境变量也能正常运行代码。但是如果想使用Ant命令批量打包本步骤必不可少。
2. 下载Ant（这里的Ant不是eclipse和android SDk里面自带的ant）
3. 解压Ant并配置环境变量
a) 解压Ant，比如解压到D:\ant
b) 我的电脑->属性->高级->环境变量
c) 系统变量新建ANT_HOME，变量值为d:\ant
d) 系统变量新建或修改PATH：将%ANT_HOME%\bin;%ANT_HOME%\lib添加到环境变量的PATH中 （注意以上
路径均用反斜杠）
4. 验证ant配置是否正确
在控制台输入Cmd 回车， ant 回车，如果出现：
Buildfile: build.xml does not exist!
Build failed
恭喜你已经ant配置成功！！
Ant批量打包的基本思想是，每次打包后自动替换渠道号，然后再次打包从而实现多渠道打包的目的。
但是Ant不支持循环，怎样循环打包？ 扩展包Ant-contrib能轻松解决这个问题.可以翻墙的1.0b3.jar放到Ant的lib文件夹即可.
5. 编写build.xml
将以下带有颜色的字体（包括路径，项目名称）都改成正确的名称
<?xml version="1.0" encoding="UTF-8"?>
<project name="ThumbPlay" default="help">
<!-- 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" />
<!-- 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 an env var"
unless="sdk.dir"
/>
<!-- extension targets. Uncomment the ones where you want to do custom work
in between standard targets -->
<!--
<target name="-pre-build">
</target>
<target name="-pre-compile">
</target>
<target name="-post-compile">
</target>
-->
<!-- 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"
-->
<!-- version-tag: 1 -->
<taskdef resource="net/sf/antcontrib/antcontrib.properties">
<classpath>
<pathelement location="D:/androidDev/batch-package-tool/ant1.8.3/lib/ant-contrib-1.0b3.jar"/>
</classpath>
</taskdef>
<import file="${sdk.dir}/tools/ant/build.xml" />
<target name="deploy">
<foreach target="modify_manifest" list="${market_channels}" param="channel" delimiter=",">
</foreach>
</target>
<target name="modify_manifest">
<!--<replaceregexp file="AndroidManifest.xml" encoding="utf-8" match="android:value="(.*)"" replace=""/>-->
<replaceregexp flags="g" byline="false">
<regexp pattern="android:name="UMENG_CHANNEL" android:value="(.*)"" />
<substitution expression="android:name="UMENG_CHANNEL" android:value="${channel}"" />
<fileset dir="" includes="AndroidManifest.xml" />
</replaceregexp>
<!--<property name="out.release.file" value="${out.absolute.dir}/${channel}.apk"/>-->
<antcall target="release"/>
<copy tofile="${gos.path}/ThumbPlay_${channel}.apk">
<fileset dir="${out.absolute.dir}/" includes="ThumbPlay-release.apk" />
</copy>
<delete includeEmptyDirs="true">
<fileset dir="${out.absolute.dir}" includes="**/*"/>
</delete>
<echo message="==========================="/>
</target>
</project>
6. 配置local.properties
sdk.dir=D:\\androidDev\\android-sdk 改成你的SDK所在的目录，注意转义字符
7. 配置ant.properties
# the config file for batch package.
application.package=com.leyou.thumb （你的apk文件的包名）
ant.project.name=ThumbPlay （你的apk文件的工程名）
java.encoding=utf-8
out.absolute.dir=C:/compile
gos.path=Z:/app-version/test （打好的渠道包要放到的目的位置）
key.store=D:/androidApk/thumbplay/thumbplay.keystore (keystore文件路径)
key.store.password=wushenshiji999 (keystore文件路径)
key.alias=muzhigame （keystore文件别名）
key.alias.password=wushenshiji999 （keystore文件别名密码）
app_version=1.0.4 （要打的渠道包的版本名称）
market_channels=guanwang,shuihu,wushen,shenhua,huawei （渠道名称，要以逗号分隔，必须在一行内）
ant 实现批量打包android应用
很多的应用中需要加上应用推广的统计，如果一个一个的去生成不同渠道包的应用，效率低不说，还有可能不小心弄错了分发渠道，使用ant可以批量生成应用。
一、添加渠道包信息
为了统计渠道信息，就不得不在程序的某个地方加入渠道的信息，然后针对不同的渠道打不同的包。一般可以在Manifest文件中加入渠道编号，而不直接写在代码中。这样做的好处是，可以针对不同渠道，自动化去修改Manifest文件中的渠道编号，然后自动为该渠道打包。
Manifest文件支持Meta Data标签，建议使用这种自定义标签。例如下面的文件片段。
[html] view plaincopyprint?
<meta-data android:value="000000" android:name="CHANNEL"/>
二、渠道包读取
[java] view plaincopyprint?
public static String getChanel(Context ctx){
String CHANNELID="000000";
try {
ApplicationInfo ai = ctx.getPackageManager().getApplicationInfo(
ctx.getPackageName(), PackageManager.GET_META_DATA);
Object value = ai.metaData.get("");
if (value != null) {
CHANNELID= value.toString();
}
} catch (Exception e) {
//
}
return CHANNELID;
}
三、自动打包实现
Ant编译android程序 简单介绍了使用ant命令打包android程序，实现批量打包需要的加一个类似于for循环的功能即可，在Ant的核心包里没有相关的For循环的Task，要下载相应的扩展包。可以使用开源的Ant-contrib包。下载地址：http://ant-contrib.sourceforge.net/ 。下载后的解压得到的jar文件放到ant的lib目录。
在build.xml中增加如下代码就可以实现批量打包：
[html] view plaincopyprint?
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">
<regexp pattern="android:value="(.*)" android:name="CHANNEL"" />
<substitution expression="android:value="${channel}" android:name="CHANNEL"" />
<fileset dir="" includes="AndroidManifest.xml" />
</replaceregexp>
<property name="out.release.file"
location="${out.absolute.dir}/${ant.project.name}_${channel}_${app_version}.apk" />
<antcall target="release" />
</target>
taskdef 声明需要放到较前位置，因为if condition也会用到此声明。
build.properties文件增加：
taskdef 声明需要放到较前位置，因为if condition也会用到此声明。
build.properties文件增加：
[html] view plaincopyprint?
market_channels=000000,012345
app_version=1.2.1
market名称用逗号分隔
执行ant deploy即可。
/**
* @author 张兴业
* 邮箱：xy-zhang#163.com
* android开发进阶群：278401545
*
*/
很多Java程序员由于使用Eclipse不配置Java环境变量也能正常运行代码。但是如果想使用Ant命令批量打包本步骤必不可少。
2. 下载Ant（这里的Ant不是eclipse和android SDk里面自带的ant）
3. 解压Ant并配置环境变量
a) 解压Ant，比如解压到D:\ant
b) 我的电脑->属性->高级->环境变量
c) 系统变量新建ANT_HOME，变量值为d:\ant
d) 系统变量新建或修改PATH：将%ANT_HOME%\bin;%ANT_HOME%\lib添加到环境变量的PATH中 （注意以上
路径均用反斜杠）
4. 验证ant配置是否正确
在控制台输入Cmd 回车， ant 回车，如果出现：
Buildfile: build.xml does not exist!
Build failed
恭喜你已经ant配置成功！！
Ant批量打包的基本思想是，每次打包后自动替换渠道号，然后再次打包从而实现多渠道打包的目的。
但是Ant不支持循环，怎样循环打包？ 扩展包Ant-contrib能轻松解决这个问题.可以翻墙的1.0b3.jar放到Ant的lib文件夹即可.
5. 编写build.xml
将以下带有颜色的字体（包括路径，项目名称）都改成正确的名称
<?xml version="1.0" encoding="UTF-8"?>
<project name="ThumbPlay" default="help">
<!-- 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" />
<!-- 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 an env var"
unless="sdk.dir"
/>
<!-- extension targets. Uncomment the ones where you want to do custom work
in between standard targets -->
<!--
<target name="-pre-build">
</target>
<target name="-pre-compile">
</target>
<target name="-post-compile">
</target>
-->
<!-- 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"
-->
<!-- version-tag: 1 -->
<taskdef resource="net/sf/antcontrib/antcontrib.properties">
<classpath>
<pathelement location="D:/androidDev/batch-package-tool/ant1.8.3/lib/ant-contrib-1.0b3.jar"/>
</classpath>
</taskdef>
<import file="${sdk.dir}/tools/ant/build.xml" />
<target name="deploy">
<foreach target="modify_manifest" list="${market_channels}" param="channel" delimiter=",">
</foreach>
</target>
<target name="modify_manifest">
<!--<replaceregexp file="AndroidManifest.xml" encoding="utf-8" match="android:value="(.*)"" replace=""/>-->
<replaceregexp flags="g" byline="false">
<regexp pattern="android:name="UMENG_CHANNEL" android:value="(.*)"" />
<substitution expression="android:name="UMENG_CHANNEL" android:value="${channel}"" />
<fileset dir="" includes="AndroidManifest.xml" />
</replaceregexp>
<!--<property name="out.release.file" value="${out.absolute.dir}/${channel}.apk"/>-->
<antcall target="release"/>
<copy tofile="${gos.path}/ThumbPlay_${channel}.apk">
<fileset dir="${out.absolute.dir}/" includes="ThumbPlay-release.apk" />
</copy>
<delete includeEmptyDirs="true">
<fileset dir="${out.absolute.dir}" includes="**/*"/>
</delete>
<echo message="==========================="/>
</target>
</project>
6. 配置local.properties
sdk.dir=D:\\androidDev\\android-sdk 改成你的SDK所在的目录，注意转义字符
7. 配置ant.properties
# the config file for batch package.
application.package=com.leyou.thumb （你的apk文件的包名）
ant.project.name=ThumbPlay （你的apk文件的工程名）
java.encoding=utf-8
out.absolute.dir=C:/compile
gos.path=Z:/app-version/test （打好的渠道包要放到的目的位置）
key.store=D:/androidApk/thumbplay/thumbplay.keystore (keystore文件路径)
key.store.password=wushenshiji999 (keystore文件路径)
key.alias=muzhigame （keystore文件别名）
key.alias.password=wushenshiji999 （keystore文件别名密码）
app_version=1.0.4 （要打的渠道包的版本名称）
market_channels=guanwang,shuihu,wushen,shenhua,huawei （渠道名称，要以逗号分隔，必须在一行内）
ant 实现批量打包android应用
很多的应用中需要加上应用推广的统计，如果一个一个的去生成不同渠道包的应用，效率低不说，还有可能不小心弄错了分发渠道，使用ant可以批量生成应用。
一、添加渠道包信息
为了统计渠道信息，就不得不在程序的某个地方加入渠道的信息，然后针对不同的渠道打不同的包。一般可以在Manifest文件中加入渠道编号，而不直接写在代码中。这样做的好处是，可以针对不同渠道，自动化去修改Manifest文件中的渠道编号，然后自动为该渠道打包。
Manifest文件支持Meta Data标签，建议使用这种自定义标签。例如下面的文件片段。
[html] view plaincopyprint?
<meta-data android:value="000000" android:name="CHANNEL"/>
二、渠道包读取
[java] view plaincopyprint?
public static String getChanel(Context ctx){
String CHANNELID="000000";
try {
ApplicationInfo ai = ctx.getPackageManager().getApplicationInfo(
ctx.getPackageName(), PackageManager.GET_META_DATA);
Object value = ai.metaData.get("");
if (value != null) {
CHANNELID= value.toString();
}
} catch (Exception e) {
//
}
return CHANNELID;
}
三、自动打包实现
Ant编译android程序 简单介绍了使用ant命令打包android程序，实现批量打包需要的加一个类似于for循环的功能即可，在Ant的核心包里没有相关的For循环的Task，要下载相应的扩展包。可以使用开源的Ant-contrib包。下载地址：http://ant-contrib.sourceforge.net/ 。下载后的解压得到的jar文件放到ant的lib目录。
在build.xml中增加如下代码就可以实现批量打包：
[html] view plaincopyprint?
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">
<regexp pattern="android:value="(.*)" android:name="CHANNEL"" />
<substitution expression="android:value="${channel}" android:name="CHANNEL"" />
<fileset dir="" includes="AndroidManifest.xml" />
</replaceregexp>
<property name="out.release.file"
location="${out.absolute.dir}/${ant.project.name}_${channel}_${app_version}.apk" />
<antcall target="release" />
</target>
taskdef 声明需要放到较前位置，因为if condition也会用到此声明。
build.properties文件增加：
taskdef 声明需要放到较前位置，因为if condition也会用到此声明。
build.properties文件增加：
[html] view plaincopyprint?
market_channels=000000,012345
app_version=1.2.1
market名称用逗号分隔
执行ant deploy即可。
/**
* @author 张兴业
* 邮箱：xy-zhang#163.com
* android开发进阶群：278401545
*
*/
