6edb5a108e
Target 'run-tests' launches all the unit tests against the tested project. Target 'coverage' emma-instruments the tested project's classes, runs the tests against instrumented classes, collects code coverage data and extracts it to human-readable form as report.html. android_test_rules.xml contain additional rules for test projects. Test projects are auto-recognized by presence of the tested.project.dir property, which will be auto-generated for tests projects. Temporarily, please add this property manually to the build.properties file. Current version is mainly tested with default, android generated test projects. This version includes also fixing relative to absolute paths for properties which are most likely to be changed by user in external property file.
68 lines
2.8 KiB
XML
68 lines
2.8 KiB
XML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<project name="PROJECT_NAME" 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 in in Version
|
|
Control Systems. -->
|
|
<property file="local.properties" />
|
|
|
|
<!-- The build.properties file can be created by you and is never touched
|
|
by the 'android' tool. This is the place to change some of the default property values
|
|
used by the Ant rules.
|
|
Here are some properties you may want to change/update:
|
|
|
|
application.package
|
|
the name of your application package as defined in the manifest. Used by the
|
|
'uninstall' rule.
|
|
source.dir
|
|
the name of the source directory. Default is 'src'.
|
|
out.dir
|
|
the name of the output directory. Default is 'bin'.
|
|
|
|
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 in in Version Control Systems.
|
|
|
|
-->
|
|
<property file="build.properties" />
|
|
|
|
<!-- The default.properties file is created and updated by the 'android' tool, as well
|
|
as ADT.
|
|
This file is an integral part of the build system for your application and
|
|
should be checked in in Version Control Systems. -->
|
|
<property file="default.properties" />
|
|
|
|
<!-- Custom Android task to deal with the project target, and import the proper rules.
|
|
This requires ant 1.6.0 or above. -->
|
|
<path id="android.antlibs">
|
|
<pathelement path="${sdk.dir}/tools/lib/anttasks.jar" />
|
|
<pathelement path="${sdk.dir}/tools/lib/sdklib.jar" />
|
|
<pathelement path="${sdk.dir}/tools/lib/androidprefs.jar" />
|
|
<pathelement path="${sdk.dir}/tools/lib/apkbuilder.jar" />
|
|
<pathelement path="${sdk.dir}/tools/lib/jarutils.jar" />
|
|
</path>
|
|
|
|
<taskdef name="setup"
|
|
classname="com.android.ant.SetupTask"
|
|
classpathref="android.antlibs" />
|
|
|
|
<!-- Execute the Android Setup task that will setup some properties specific to the target,
|
|
and import the build rules files.
|
|
|
|
The rules file is imported from
|
|
<SDK>/platforms/<target_platform>/templates/android_rules.xml
|
|
|
|
To customize some build steps for your project:
|
|
- copy the content of the main node <project> from android_rules.xml
|
|
- paste it in this build.xml below the <setup /> task.
|
|
- disable the import by changing the setup task below to <setup import="false" />
|
|
|
|
This will ensure that the properties are setup correctly but that your customized
|
|
build steps are used.
|
|
-->
|
|
<setup />
|
|
|
|
</project>
|