Hacking A Startup DroidRules HackedLabs Posts My Google KnolsA firm has begun trademark application review process on the mobilebytes name i the mobile applications field so I am transitioning the blog to;
So change your bookmarks, new android stuff will be posted soon and will still be posting about eclipse, linux, java, startups, etc. Onplanet android the android feed will change to:
http://fredgrott.wordpress.com/category/android/feed/
So if you consume the rss as individual feed put into your rss reader now.
The Android 2.2 Sdk release is probably on Wed morning. But, this sdk release is different.
Not only do we have a quarter where android device sales surpassed iphone(remember I told you it was going to happen in 2010 not 2011), we also have an Android SDK that represents both Google and OHA taking outside suggestions and incorporating that into the SDK. Such improvements as a Dalvik Just-In-time(JIT) unit and being able to store applications on a SD-card.
![Reblog this post [with Zemanta]](https://i0.wp.com/img.zemanta.com/reblog_e.png)
You may wonder why we use PMD rulesets. Remember that to have one code base targeting Android 1.5, 1.6, and 2.x you have to use a minSDK of 3 and targetSDK of 4 in the manifest? So how od you get your IDE to warn you when using certain 1.6 calls when you should be using 1.5 calls?
<rule name="DoNotCodebuildStringDetectOneSix" message="Do not code detect build string as 1.6 but as 1.5" class="net.sourceforge.pmd.rules.XPathRule">
<description>do not use getApplicationInfo().targetSdkVersion use int sdkVersion = Integer.parseInt(Build.VERSION.SDK); instead</description>
<priority>3</priority>
<properties>
<property name="xpath">
<value>//Literal[starts-with(@Image,’getApplicationInfo().targetSdkVersion ‘)]</value>
</property>
</properties>
</rule>
That little rule prevents you form using the android 1.6 style of detecting a build string and forces you to use the 1.5 style of detecting a build string
The problem happens to be that every UI implementation on the OS side has a different color color sets for focused and selected. HTC Sense is green, Android SDK is orange, and both Moto Blur and SonyEricsson Rachel are different colors.
On top of that not only are the image button colors changed but the hight light colors as well. Seems to me that if you could detect the build OS string to detect different UI implementations than set a theme:
setTheme(android.R.style.Theme_Dark); // ... setContentView(R.layout.main);
Bu t than you still have to change all your button and tabs etc. You still could use selectors but you would have an image set for each UI OS implementation and use an if then wrap code to select based on the build string.
Since most android training course do not cover these types of issues and solutions maybe you should bookmark those Android Knol collections links at the right side of this blog.
I have a refactoring of AndCooper ANY build for Android applications:
<?xml version="1.0" encoding="UTF-8"?>
<!-- ======================================================================
Feb 2, 2010 12:22:12 PM
AndroidAppANTBuild
Build file to build Android Applications
fredgrott
====================================================================== -->
<project name="AndroidAppANTBuild" default="help" basedir=".">
<description>
Build file to build Android Applications, not the apps test build
</description>
<property environment="env"/>
<tstamp/>
<!-- The local.properties file is created and updated by the 'android' tool.
It contains the path to the SDK and the framework.aidl file and
the platform version tools folder and the sdk tols folder. It should
*NOT* be checked in in Version
Control Systems.
sdk-location
sdk-tools-location
sdk-platform-location
sdk-platform-tools-location
sdk-aidl-location
tested.project.dir
-->
<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-tools-location}/lib/anttasks.jar" />
<pathelement path="${sdk-tools-location}/lib/sdklib.jar" />
<pathelement path="${sdk-tools-location}/lib/androidprefs.jar" />
<pathelement path="${sdk-tools-location}/lib/apkbuilder.jar" />
<pathelement path="${sdk-tools-location}/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 import="false" />
<!-- Custom tasks -->
<taskdef name="aaptexec"
classname="com.android.ant.AaptExecLoopTask"
classpathref="android.antlibs" />
<taskdef name="apkbuilder"
classname="com.android.ant.ApkBuilderTask"
classpathref="android.antlibs" />
<taskdef name="xpath"
classname="com.android.ant.XPathTask"
classpathref="android.antlibs" />
<!-- Tells adb which device to target. You can change this from the command line
by invoking "ant -Dadb.device.arg=-d" for device "ant -Dadb.device.arg=-e" for
the emulator. -->
<property name="adb.device.arg" value="" />
<property name="android.tools.dir" location="${sdk-tools-location}" />
<property name="tested.project.absolute.dir" location="${tested.project.dir}" />
<property name="instrumentation.dir" value="instrumented" />
<property name="instrumentation.absolute.dir" location="${instrumentation.dir}" />
<property name="test.runner" value="android.test.InstrumentationTestRunner" />
<property name="android.aidl" value="${sdk-aidl-location}"/>
<!-- TODO: make it more configurable in the next CL's - now it is default for auto-generated
project -->
<property name="emma.dump.file"
value="/data/data/${tested.manifest.package}/files/coverage.ec" />
<!-- Name of the application package extracted from manifest file -->
<xpath input="AndroidManifest.xml" expression="/manifest/@package"
output="manifest.package" />
<xpath input="${tested.project.absolute.dir}/AndroidManifest.xml"
expression="/manifest/@package" output="tested.manifest.package" />
<!-- Input directories -->
<property name="source.dir" value="${source-folder}" />
<property name="source.absolute.dir" location="${source.dir}" />
<property name="gen.dir" value="gen" />
<property name="gen.absolute.dir" location="${gen.dir}" />
<property name="resource.dir" value="res" />
<property name="resource.absolute.dir" location="${resource.dir}" />
<property name="asset.dir" value="assets" />
<property name="asset.absolute.dir" location="${asset.dir}" />
<!-- Directory for the third party java libraries -->
<property name="external.libs.dir" value="libs" />
<property name="external.libs.absolute.dir" location="${external.libs.dir}" />
<!-- Directory for the native libraries -->
<property name="native.libs.dir" value="libs" />
<property name="native.libs.absolute.dir" location="${native.libs.dir}" />
<!-- Output directories -->
<property name="out.dir" value="${out-folder}" />
<property name="out.absolute.dir" location="${out.dir}" />
<property name="out.classes.dir" value="${out.absolute.dir}/classes" />
<property name="out.classes.absolute.dir" location="${out.classes.dir}" />
<!-- Intermediate files -->
<property name="dex.file.name" value="classes.dex" />
<property name="intermediate.dex.file" location="${out.absolute.dir}/${dex.file.name}" />
<!-- The final package file to generate -->
<property name="out.debug.unaligned.package"
location="${out.absolute.dir}/${ant.project.name}-debug-unaligned.apk" />
<property name="out.debug.package"
location="${out.absolute.dir}/${ant.project.name}-debug.apk" />
<property name="out.unsigned.package"
location="${out.absolute.dir}/${ant.project.name}-unsigned.apk" />
<property name="out.unaligned.package"
location="${out.absolute.dir}/${ant.project.name}-unaligned.apk" />
<property name="out.release.package"
location="${out.absolute.dir}/${ant.project.name}-release.apk" />
<!-- Verbosity -->
<property name="verbose" value="false" />
<!-- This is needed by emma as it uses multilevel verbosity instead of simple 'true' or 'false'
The property 'verbosity' is not user configurable and depends exclusively on 'verbose'
value.-->
<condition property="verbosity" value="verbose" else="quiet">
<istrue value="${verbose}" />
</condition>
<!-- This is needed to switch verbosity of zipalign and aapt. Depends exclusively on 'verbose'
-->
<condition property="v.option" value="-v" else="">
<istrue value="${verbose}" />
</condition>
<!-- This is needed to switch verbosity of dx. Depends exclusively on 'verbose' -->
<condition property="verbose.option" value="--verbose" else="">
<istrue value="${verbose}" />
</condition>
<!-- Tools -->
<condition property="exe" value=".exe" else=""><os family="windows" /></condition>
<property name="adb" location="${android.tools.dir}/adb${exe}" />
<property name="zipalign" location="${android.tools.dir}/zipalign${exe}" />
<!-- Emma configuration -->
<property name="emma.dir" value="${sdk-tools-location}/lib" />
<path id="emma.lib">
<pathelement location="${emma.dir}/emma.jar" />
<pathelement location="${emma.dir}/emma_ant.jar" />
</path>
<taskdef resource="emma_ant.properties" classpathref="emma.lib" />
<!-- End of emma configuration -->
<!-- Configurable macro, which allows to pass as parameters output directory,
output dex filename and external libraries to dex (optional) -->
<macrodef name="dex-helper">
<element name="external-libs" optional="yes" />
<element name="extra-parameters" optional="yes" />
<sequential>
<echo>Converting compiled files and external libraries into ${intermediate.dex.file}...
</echo>
<apply executable="${dx}" failonerror="true" parallel="true">
<arg value="--dex" />
<arg value="--output=${intermediate.dex.file}" />
<extra-parameters />
<arg line="${verbose.option}" />
<arg path="${out.classes.absolute.dir}" />
<fileset dir="${external.libs.absolute.dir}" includes="*.jar" />
<external-libs />
</apply>
</sequential>
</macrodef>
<!-- This is macro that enable passing variable list of external jar files to ApkBuilder
Example of use:
<package-helper>
<extra-jars>
<jarfolder path="my_jars" />
<jarfile path="foo/bar.jar" />
<jarfolder path="your_jars" />
</extra-jars>
</package-helper> -->
<macrodef name="package-helper">
<attribute name="sign.package" />
<element name="extra-jars" optional="yes" />
<sequential>
<apkbuilder
outfolder="${out.absolute.dir}"
basename="${ant.project.name}"
signed="@{sign.package}"
verbose="${verbose}">
<file path="${intermediate.dex.file}" />
<sourcefolder path="${source.absolute.dir}" />
<nativefolder path="${native.libs.absolute.dir}" />
<jarfolder path="${external.libs.absolute.dir}" />
<extra-jars/>
</apkbuilder>
</sequential>
</macrodef>
<!-- This is macro which zipaligns in.package and outputs it to out.package. Used by targets
debug, -debug-with-emma and release.-->
<macrodef name="zipalign-helper">
<attribute name="in.package" />
<attribute name="out.package" />
<sequential>
<echo>Running zip align on final apk...</echo>
<exec executable="${zipalign}" failonerror="true">
<arg line="${v.option}" />
<arg value="-f" />
<arg value="4" />
<arg path="@{in.package}" />
<arg path="@{out.package}" />
</exec>
</sequential>
</macrodef>
<!-- This is macro used only for sharing code among two targets, -install and
-install-with-emma which do exactly the same but differ in dependencies -->
<macrodef name="install-helper">
<sequential>
<echo>Installing ${out.debug.package} onto default emulator or device...</echo>
<exec executable="${adb}" failonerror="true">
<arg line="${adb.device.arg}" />
<arg value="install" />
<arg value="-r" />
<arg path="${out.debug.package}" />
</exec>
</sequential>
</macrodef>
<macrodef name="run-tests-helper">
<attribute name="emma.enabled" default="false" />
<element name="extra-instrument-args" optional="yes" />
<sequential>
<echo>Running tests ...</echo>
<exec executable="${adb}" failonerror="true">
<arg value="shell" />
<arg value="am" />
<arg value="instrument" />
<arg value="-w" />
<arg value="-e" />
<arg value="coverage" />
<arg value="@{emma.enabled}" />
<extra-instrument-args />
<arg value="${manifest.package}/${test.runner}" />
</exec>
</sequential>
</macrodef>
<!-- - - - - - - - - - - - - - - - - - -
target: -dirs
Creates the output directories if they
don't exist yet.
- - - - - - - - - - - - - - - - - - -->
<target name="-dirs">
<echo>Creating output directories if needed...</echo>
<mkdir dir="${resource.absolute.dir}" />
<mkdir dir="${external.libs.absolute.dir}" />
<mkdir dir="${gen.absolute.dir}" />
<mkdir dir="${out.absolute.dir}" />
<mkdir dir="${out.classes.absolute.dir}" />
</target>
<!-- - - - - - - - - - - - - - - - - - -
target: -resource-src
Generates the R.java file for this
project's resources.
- - - - - - - - - - - - - - - - - - -->
<target name="-resource-src" depends="-dirs">
<echo>Generating R.java / Manifest.java from the resources...</echo>
<exec executable="${aapt}" failonerror="true">
<arg value="package" />
<arg line="${v.option}" />
<arg value="-m" />
<arg value="-J" />
<arg path="${gen.absolute.dir}" />
<arg value="-M" />
<arg path="AndroidManifest.xml" />
<arg value="-S" />
<arg path="${resource.absolute.dir}" />
<arg value="-I" />
<arg path="${android.jar}" />
</exec>
</target>
<!-- - - - - - - - - - - - - - - - -
target: -aidl
Generates java classes from .aidl files.
- - - - - - - - - - - - - - - - -->
<target name="-aidl" depends="-dirs">
<echo>Compiling aidl files into Java classes...</echo>
<apply executable="${aidl}" failonerror="true">
<arg value="-p${android.aidl}" />
<arg value="-I${source.absolute.dir}" />
<arg value="-o${gen.absolute.dir}" />
<fileset dir="${source.absolute.dir}">
<include name="**/*.aidl" />
</fileset>
</apply>
</target>
<!-- - - - - - - - - - - - - - - - - - - - - -
target: compile
Compiles this project's .java files
into .class files.
- - - - - - - - - - - - - - - - - - - - - -->
<target name="compile" depends="-resource-src, -aidl"
description="Compiles project's .java files into .class files">
<!-- If android rules are used for a test project, its classpath should include
tested project's location -->
<condition property="extensible.classpath"
value="${tested.project.absolute.dir}/bin/classes" else=".">
<isset property="tested.project.absolute.dir" />
</condition>
<javac encoding="ascii" target="1.5" debug="true" extdirs=""
destdir="${out.classes.absolute.dir}"
bootclasspathref="android.target.classpath"
verbose="${verbose}" classpath="${extensible.classpath}">
<src path="${source.absolute.dir}" />
<src path="${gen.absolute.dir}" />
<classpath>
<fileset dir="${external.libs.absolute.dir}" includes="*.jar" />
</classpath>
</javac>
</target>
<!-- - - - - - - - - - - - - - - - - - - - - -
target: -dex
Converts this project's .class files
into .dex files
- - - - - - - - - - - - - - - - - - - - - -->
<target name="-dex" depends="compile">
<dex-helper />
</target>
<!-- - - - - - - - - - - - - - - - - - - - - -
target: -package-resources
Puts the project's resources into the
output package file This actually can
create multiple resource package in case
Some custom apk with specific configuration have been
declared in default.properties.
- - - - - - - - - - - - - - - - - - - - - -->
<target name="-package-resources">
<echo>Packaging resources</echo>
<aaptexec executable="${aapt}"
command="package"
manifest="AndroidManifest.xml"
resources="${resource.absolute.dir}"
assets="${asset.absolute.dir}"
androidjar="${android.jar}"
outfolder="${out.absolute.dir}"
basename="${ant.project.name}" />
</target>
<!-- - - - - - - - - - - - - - - - - - - - -
target: -package-debug-sign
Packages the application and sign
it with a debug key.
- - - - - - - - - - - - - - - - - - - - -->
<target name="-package-debug-sign" depends="-dex, -package-resources">
<package-helper sign.package="true" />
</target>
<!-- - - - - - - - - - - - - - - - - - - -
target: -package-no-sign
Packages the application without
signing it.
- - - - - - - - - - - - - - - - - - - -->
<target name="-package-no-sign" depends="-dex, -package-resources">
<package-helper sign.package="false" />
</target>
<!-- - - - - - - - - - - - - - - - - - - - - - -
target: -compile-if-tested-if-test
- - - - - - - - - - - - - - - - - - - - - - -->
<target name="-compile-tested-if-test" if="tested.project.dir" unless="do.not.compile.again">
<subant target="compile">
<fileset dir="${tested.project.absolute.dir}" includes="build.xml" />
</subant>
</target>
<!-- ========================================
target: debug
Builds debug output package, provided
all the necessary files are already dexed
======================================== -->
<target name="debug" depends="-compile-tested-if-test, -package-debug-sign"
description="Builds the application and signs it with a debug key.">
<zipalign-helper in.package="${out.debug.unaligned.package}"
out.package="${out.debug.package}" />
<echo>Debug Package: ${out.debug.package}</echo>
</target>
<!-- - - - - - - - - - - - - - - - - - -
target: -release-check
- - - - - - - - - - - - - - - - - - -->
<target name="-release-check">
<condition property="release.sign">
<and>
<isset property="key.store" />
<isset property="key.alias" />
</and>
</condition>
</target>
<!-- - - - - - - - - - - - - - - - - - -
target: -release-nosign
- - - - - - - - - - - - - - - - - - -->
<target name="-release-nosign" depends="-release-check" unless="release.sign">
<echo>No key.store and key.alias properties found in build.properties.</echo>
<echo>Please sign ${out.unsigned.package} manually</echo>
<echo>and run zipalign from the Android SDK tools.</echo>
</target>
<!-- ======================================
target: release
====================================== -->
<target name="release" depends="-package-no-sign, -release-nosign" if="release.sign"
description="Builds the application. The generated apk file must be signed before
it is published.">
<!-- Gets passwords -->
<input
message="Please enter keystore password (store:${key.store}):"
addproperty="key.store.password" />
<input
message="Please enter password for alias '${key.alias}':"
addproperty="key.alias.password" />
<!-- Signs the APK -->
<echo>Signing final apk...</echo>
<signjar
jar="${out.unsigned.package}"
signedjar="${out.unaligned.package}"
keystore="${key.store}"
storepass="${key.store.password}"
alias="${key.alias}"
keypass="${key.alias.password}"
verbose="${verbose}" />
<!-- Zip aligns the APK -->
<zipalign-helper in.package="${out.unaligned.package}"
out.package="${out.release.package}" />
<echo>Release Package: ${out.release.package}</echo>
</target>
<!-- ===========================
target: install
=========================== -->
<target name="install" depends="debug"
description="Installs/reinstalls the debug package onto a running
emulator or device. If the application was previously installed,
the signatures must match." >
<install-helper />
</target>
<!-- - - - - - - - - - - - - - - - - - - - - -
target: -uninstall-check
- - - - - - - - - - - - - - - - - - - - - -->
<target name="-uninstall-check">
<condition property="uninstall.run">
<isset property="manifest.package" />
</condition>
</target>
<!-- - - - - - - - - - - - - - - - - - - - - -
target: -uninstall-error
- - - - - - - - - - - - - - - - - - - - - -->
<target name="-uninstall-error" depends="-uninstall-check" unless="uninstall.run">
<echo>Unable to run 'ant uninstall', manifest.package property is not defined.
</echo>
</target>
<!-- ====================================
target: unistall
Uninstalls the package from the
default emulator/device
==================================== -->
<target name="uninstall" depends="-uninstall-error" if="uninstall.run"
description="Uninstalls the application from a running emulator or device.">
<echo>Uninstalling ${manifest.package} from the default emulator or device...</echo>
<exec executable="${adb}" failonerror="true">
<arg line="${adb.device.arg}" />
<arg value="uninstall" />
<arg value="${manifest.package}" />
</exec>
</target>
<!-- ====================================
target: clean
==================================== -->
<target name="clean" description="Removes output files created by other targets.">
<delete dir="${out.absolute.dir}" verbose="${verbose}" />
<delete dir="${gen.absolute.dir}" verbose="${verbose}" />
</target>
<!-- Targets for code-coverage measurement purposes, invoked from external file -->
<!-- - - - - - - - - - - - - - - - - -
target: -emma-instrument
Emma-instruments tested project
classes (compiles the tested
project if necessary)
and writes instrumented classes
to ${instrumentation.absolute.dir}/classes
- - - - - - - - - - - - - - - - - -->
<target name="-emma-instrument" depends="compile">
<echo>Instrumenting classes from ${out.absolute.dir}/classes...</echo>
<!-- It only instruments class files, not any external libs -->
<emma enabled="true">
<instr verbosity="${verbosity}"
mode="overwrite"
instrpath="${out.absolute.dir}/classes"
outdir="${out.absolute.dir}/classes">
</instr>
<!-- TODO: exclusion filters on R*.class and allowing custom exclusion from
user defined file -->
</emma>
</target>
<!-- - - - - - - - - - - - - - - - - -
target: -dex-instrumented
- - - - - - - - - - - - - - - - - -->
<target name="-dex-instrumented" depends="-emma-instrument">
<dex-helper>
<extra-parameters>
<arg value="--no-locals" />
</extra-parameters>
<external-libs>
<fileset file="${emma.dir}/emma_device.jar" />
</external-libs>
</dex-helper>
</target>
<!-- - - - - - - - - - - - - - - - - -
target: -package-with-emma
Invoked from external files for
code coverage purposes
- - - - - - - - - - - - - - - - - -->
<target name="-package-with-emma" depends="-dex-instrumented, -package-resources">
<package-helper sign.package="true">
<extra-jars>
<!-- Injected from external file -->
<jarfile path="${emma.dir}/emma_device.jar" />
</extra-jars>
</package-helper>
</target>
<!-- - - - - - - - - - - - - - - - - -
target: -debug-with-emma
- - - - - - - - - - - - - - - - - -->
<target name="-debug-with-emma" depends="-package-with-emma">
<zipalign-helper in.package="${out.debug.unaligned.package}"
out.package="${out.debug.package}" />
</target>
<!-- ======================================
target: -install-with-emma
====================================== -->
<target name="-install-with-emma" depends="-debug-with-emma">
<install-helper />
</target>
<!-- End of targets for code-coverage measurement purposes -->
<!-- ======================================
target: help
====================================== -->
<target name="help">
<!-- displays starts at col 13
|13 80| -->
<echo>Android Ant Build. Available targets:</echo>
<echo> help: Displays this help.</echo>
<echo> clean: Removes output files created by other targets.</echo>
<echo> compile: Compiles project's .java files into .class files.</echo>
<echo> debug: Builds the application and signs it with a debug key.</echo>
<echo> release: Builds the application. The generated apk file must be</echo>
<echo> signed before it is published.</echo>
<echo> install: Installs/reinstalls the debug package onto a running</echo>
<echo> emulator or device.</echo>
<echo> If the application was previously installed, the</echo>
<echo> signatures must match.</echo>
<echo> uninstall: Uninstalls the application from a running emulator or</echo>
<echo> device.</echo>
<echo> run-tests: Runs EMMA tests</echo>
<echo> coverage: Runs coverage report</echo>
</target>
<!-- - - - - - - - - - - - - - - - - - - - -
target: -set-coverage-classpath
Invoking this target sets the value of
extensible.classpath, which is being added to javac
classpath in target 'compile' (android_rules.xml)
- - - - - - - - - - - - - - - - - - - - -->
<target name="-set-coverage-classpath">
<property name="extensible.classpath"
location="${instrumentation.absolute.dir}/classes" />
</target>
<!-- - - - - - - - - - - - - - - - - - - - - - - -
target: -install-tested-project
Ensures that tested project is installed on
the device before we run the tests.
Used for ordinary tests, without coverage measurement
- - - - - - - - - - - - - - - - - - - - - - - -->
<target name="-install-tested-project">
<property name="do.not.compile.again" value="true" />
<subant target="install">
<fileset dir="${tested.project.absolute.dir}" includes="build.xml" />
</subant>
</target>
<!-- ====================================
target: run-tests
==================================== -->
<target name="run-tests" depends="-install-tested-project, install"
description="Runs tests from the package defined in test.package property">
<run-tests-helper />
</target>
<!-- - - - - - - - - - - - - - - - -
target: -install-instrumented
- - - - - - - - - - - - - - - - -->
<target name="-install-instrumented">
<property name="do.not.compile.again" value="true" />
<subant target="-install-with-emma">
<property name="out.absolute.dir" value="${instrumentation.absolute.dir}" />
<fileset dir="${tested.project.absolute.dir}" includes="build.xml" />
</subant>
</target>
<!-- ===============================================
target: coverage
=============================================== -->
<target name="coverage" depends="-set-coverage-classpath, -install-instrumented, install"
description="Runs the tests against the instrumented code and generates
code coverage report">
<run-tests-helper emma.enabled="true">
<extra-instrument-args>
<arg value="-e" />
<arg value="coverageFile" />
<arg value="${emma.dump.file}" />
</extra-instrument-args>
</run-tests-helper>
<echo>Downloading coverage file into project directory...</echo>
<exec executable="${adb}" failonerror="true">
<arg value="pull" />
<arg value="${emma.dump.file}" />
<arg value="coverage.ec" />
</exec>
<echo>Extracting coverage report...</echo>
<emma>
<report sourcepath="${tested.project.absolute.dir}/${source.dir}"
verbosity="${verbosity}">
<!-- TODO: report.dir or something like should be introduced if necessary -->
<infileset dir=".">
<include name="coverage.ec" />
<include name="coverage.em" />
</infileset>
<!-- TODO: reports in other, indicated by user formats -->
<html outfile="coverage.html" />
</report>
</emma>
<echo>Cleaning up temporary files...</echo>
<delete dir="${instrumentation.absolute.dir}" />
<delete file="coverage.ec" />
<delete file="coverage.em" />
<echo>Saving the report file in ${basedir}/coverage/coverage.html</echo>
</target>
</project>
<?xml version="1.0" encoding="UTF-8"?><!-- ====================================================================== Feb 2, 2010 12:22:12 PM
AndroidAppANTBuild Build file to build Android Applications fredgrott ====================================================================== --><project name="AndroidAppANTBuild" default="help" basedir="."> <description> Build file to build Android Applications, not the apps test build </description> <property environment="env"/> <tstamp/>
<!-- The local.properties file is created and updated by the 'android' tool. It contains the path to the SDK and the framework.aidl file and the platform version tools folder and the sdk tols folder. It should *NOT* be checked in in Version Control Systems. sdk-location sdk-tools-location sdk-platform-location sdk-platform-tools-location sdk-aidl-location tested.project.dir --> <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-tools-location}/lib/anttasks.jar" /> <pathelement path="${sdk-tools-location}/lib/sdklib.jar" /> <pathelement path="${sdk-tools-location}/lib/androidprefs.jar" /> <pathelement path="${sdk-tools-location}/lib/apkbuilder.jar" /> <pathelement path="${sdk-tools-location}/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 import="false" />
<!-- Custom tasks --> <taskdef name="aaptexec" classname="com.android.ant.AaptExecLoopTask" classpathref="android.antlibs" />
<taskdef name="apkbuilder" classname="com.android.ant.ApkBuilderTask" classpathref="android.antlibs" />
<taskdef name="xpath" classname="com.android.ant.XPathTask" classpathref="android.antlibs" /> <!-- Tells adb which device to target. You can change this from the command line by invoking "ant -Dadb.device.arg=-d" for device "ant -Dadb.device.arg=-e" for the emulator. --> <property name="adb.device.arg" value="" /> <property name="android.tools.dir" location="${sdk-tools-location}" /> <property name="tested.project.absolute.dir" location="${tested.project.dir}" /> <property name="instrumentation.dir" value="instrumented" /> <property name="instrumentation.absolute.dir" location="${instrumentation.dir}" />
<property name="test.runner" value="android.test.InstrumentationTestRunner" /> <property name="android.aidl" value="${sdk-aidl-location}"/> <!-- TODO: make it more configurable in the next CL's - now it is default for auto-generated project --> <property name="emma.dump.file" value="/data/data/${tested.manifest.package}/files/coverage.ec" />
<!-- Name of the application package extracted from manifest file --> <xpath input="AndroidManifest.xml" expression="/manifest/@package" output="manifest.package" /> <xpath input="${tested.project.absolute.dir}/AndroidManifest.xml" expression="/manifest/@package" output="tested.manifest.package" /> <!-- Input directories --> <property name="source.dir" value="${source-folder}" /> <property name="source.absolute.dir" location="${source.dir}" /> <property name="gen.dir" value="gen" /> <property name="gen.absolute.dir" location="${gen.dir}" /> <property name="resource.dir" value="res" /> <property name="resource.absolute.dir" location="${resource.dir}" /> <property name="asset.dir" value="assets" /> <property name="asset.absolute.dir" location="${asset.dir}" /> <!-- Directory for the third party java libraries --> <property name="external.libs.dir" value="libs" /> <property name="external.libs.absolute.dir" location="${external.libs.dir}" />
<!-- Directory for the native libraries --> <property name="native.libs.dir" value="libs" /> <property name="native.libs.absolute.dir" location="${native.libs.dir}" />
<!-- Output directories --> <property name="out.dir" value="${out-folder}" /> <property name="out.absolute.dir" location="${out.dir}" /> <property name="out.classes.dir" value="${out.absolute.dir}/classes" /> <property name="out.classes.absolute.dir" location="${out.classes.dir}" />
<!-- Intermediate files --> <property name="dex.file.name" value="classes.dex" /> <property name="intermediate.dex.file" location="${out.absolute.dir}/${dex.file.name}" />
<!-- The final package file to generate --> <property name="out.debug.unaligned.package" location="${out.absolute.dir}/${ant.project.name}-debug-unaligned.apk" /> <property name="out.debug.package" location="${out.absolute.dir}/${ant.project.name}-debug.apk" /> <property name="out.unsigned.package" location="${out.absolute.dir}/${ant.project.name}-unsigned.apk" /> <property name="out.unaligned.package" location="${out.absolute.dir}/${ant.project.name}-unaligned.apk" /> <property name="out.release.package" location="${out.absolute.dir}/${ant.project.name}-release.apk" />
<!-- Verbosity --> <property name="verbose" value="false" /> <!-- This is needed by emma as it uses multilevel verbosity instead of simple 'true' or 'false' The property 'verbosity' is not user configurable and depends exclusively on 'verbose' value.--> <condition property="verbosity" value="verbose" else="quiet"> <istrue value="${verbose}" /> </condition> <!-- This is needed to switch verbosity of zipalign and aapt. Depends exclusively on 'verbose' --> <condition property="v.option" value="-v" else=""> <istrue value="${verbose}" /> </condition> <!-- This is needed to switch verbosity of dx. Depends exclusively on 'verbose' --> <condition property="verbose.option" value="--verbose" else=""> <istrue value="${verbose}" /> </condition>
<!-- Tools --> <condition property="exe" value=".exe" else=""><os family="windows" /></condition> <property name="adb" location="${android.tools.dir}/adb${exe}" /> <property name="zipalign" location="${android.tools.dir}/zipalign${exe}" />
<!-- Emma configuration --> <property name="emma.dir" value="${sdk-tools-location}/lib" /> <path id="emma.lib"> <pathelement location="${emma.dir}/emma.jar" /> <pathelement location="${emma.dir}/emma_ant.jar" /> </path> <taskdef resource="emma_ant.properties" classpathref="emma.lib" /> <!-- End of emma configuration --> <!-- Configurable macro, which allows to pass as parameters output directory, output dex filename and external libraries to dex (optional) --> <macrodef name="dex-helper"> <element name="external-libs" optional="yes" /> <element name="extra-parameters" optional="yes" /> <sequential> <echo>Converting compiled files and external libraries into ${intermediate.dex.file}... </echo> <apply executable="${dx}" failonerror="true" parallel="true"> <arg value="--dex" /> <arg value="--output=${intermediate.dex.file}" /> <extra-parameters /> <arg line="${verbose.option}" /> <arg path="${out.classes.absolute.dir}" /> <fileset dir="${external.libs.absolute.dir}" includes="*.jar" /> <external-libs /> </apply> </sequential> </macrodef> <!-- This is macro that enable passing variable list of external jar files to ApkBuilder Example of use: <package-helper> <extra-jars> <jarfolder path="my_jars" /> <jarfile path="foo/bar.jar" /> <jarfolder path="your_jars" /> </extra-jars> </package-helper> --> <macrodef name="package-helper"> <attribute name="sign.package" /> <element name="extra-jars" optional="yes" /> <sequential> <apkbuilder outfolder="${out.absolute.dir}" basename="${ant.project.name}" signed="@{sign.package}" verbose="${verbose}"> <file path="${intermediate.dex.file}" /> <sourcefolder path="${source.absolute.dir}" /> <nativefolder path="${native.libs.absolute.dir}" /> <jarfolder path="${external.libs.absolute.dir}" /> <extra-jars/> </apkbuilder> </sequential> </macrodef> <!-- This is macro which zipaligns in.package and outputs it to out.package. Used by targets debug, -debug-with-emma and release.--> <macrodef name="zipalign-helper"> <attribute name="in.package" /> <attribute name="out.package" /> <sequential> <echo>Running zip align on final apk...</echo> <exec executable="${zipalign}" failonerror="true"> <arg line="${v.option}" /> <arg value="-f" /> <arg value="4" /> <arg path="@{in.package}" /> <arg path="@{out.package}" /> </exec> </sequential> </macrodef>
<!-- This is macro used only for sharing code among two targets, -install and -install-with-emma which do exactly the same but differ in dependencies --> <macrodef name="install-helper"> <sequential> <echo>Installing ${out.debug.package} onto default emulator or device...</echo> <exec executable="${adb}" failonerror="true"> <arg line="${adb.device.arg}" /> <arg value="install" /> <arg value="-r" /> <arg path="${out.debug.package}" /> </exec> </sequential> </macrodef> <macrodef name="run-tests-helper"> <attribute name="emma.enabled" default="false" /> <element name="extra-instrument-args" optional="yes" /> <sequential> <echo>Running tests ...</echo> <exec executable="${adb}" failonerror="true"> <arg value="shell" /> <arg value="am" /> <arg value="instrument" /> <arg value="-w" /> <arg value="-e" /> <arg value="coverage" /> <arg value="@{emma.enabled}" /> <extra-instrument-args /> <arg value="${manifest.package}/${test.runner}" /> </exec> </sequential> </macrodef>
<!-- - - - - - - - - - - - - - - - - - - target: -dirs Creates the output directories if they don't exist yet. - - - - - - - - - - - - - - - - - - --> <target name="-dirs"> <echo>Creating output directories if needed...</echo> <mkdir dir="${resource.absolute.dir}" /> <mkdir dir="${external.libs.absolute.dir}" /> <mkdir dir="${gen.absolute.dir}" /> <mkdir dir="${out.absolute.dir}" /> <mkdir dir="${out.classes.absolute.dir}" /> </target>
<!-- - - - - - - - - - - - - - - - - - - target: -resource-src Generates the R.java file for this project's resources. - - - - - - - - - - - - - - - - - - --> <target name="-resource-src" depends="-dirs"> <echo>Generating R.java / Manifest.java from the resources...</echo> <exec executable="${aapt}" failonerror="true"> <arg value="package" /> <arg line="${v.option}" /> <arg value="-m" /> <arg value="-J" /> <arg path="${gen.absolute.dir}" /> <arg value="-M" /> <arg path="AndroidManifest.xml" /> <arg value="-S" /> <arg path="${resource.absolute.dir}" /> <arg value="-I" /> <arg path="${android.jar}" /> </exec> </target>
<!-- - - - - - - - - - - - - - - - - target: -aidl Generates java classes from .aidl files. - - - - - - - - - - - - - - - - --> <target name="-aidl" depends="-dirs"> <echo>Compiling aidl files into Java classes...</echo> <apply executable="${aidl}" failonerror="true"> <arg value="-p${android.aidl}" /> <arg value="-I${source.absolute.dir}" /> <arg value="-o${gen.absolute.dir}" /> <fileset dir="${source.absolute.dir}"> <include name="**/*.aidl" /> </fileset> </apply> </target>
<!-- - - - - - - - - - - - - - - - - - - - - - target: compile Compiles this project's .java files into .class files. - - - - - - - - - - - - - - - - - - - - - --> <target name="compile" depends="-resource-src, -aidl" description="Compiles project's .java files into .class files"> <!-- If android rules are used for a test project, its classpath should include tested project's location --> <condition property="extensible.classpath" value="${tested.project.absolute.dir}/bin/classes" else="."> <isset property="tested.project.absolute.dir" /> </condition> <javac encoding="ascii" target="1.5" debug="true" extdirs="" destdir="${out.classes.absolute.dir}" bootclasspathref="android.target.classpath" verbose="${verbose}" classpath="${extensible.classpath}"> <src path="${source.absolute.dir}" /> <src path="${gen.absolute.dir}" /> <classpath> <fileset dir="${external.libs.absolute.dir}" includes="*.jar" /> </classpath> </javac> </target>
<!-- - - - - - - - - - - - - - - - - - - - - - target: -dex Converts this project's .class files into .dex files - - - - - - - - - - - - - - - - - - - - - --> <target name="-dex" depends="compile"> <dex-helper /> </target>
<!-- - - - - - - - - - - - - - - - - - - - - - target: -package-resources Puts the project's resources into the output package file This actually can create multiple resource package in case Some custom apk with specific configuration have been declared in default.properties. - - - - - - - - - - - - - - - - - - - - - --> <target name="-package-resources"> <echo>Packaging resources</echo> <aaptexec executable="${aapt}" command="package" manifest="AndroidManifest.xml" resources="${resource.absolute.dir}" assets="${asset.absolute.dir}" androidjar="${android.jar}" outfolder="${out.absolute.dir}" basename="${ant.project.name}" /> </target>
<!-- - - - - - - - - - - - - - - - - - - - - target: -package-debug-sign Packages the application and sign it with a debug key. - - - - - - - - - - - - - - - - - - - - --> <target name="-package-debug-sign" depends="-dex, -package-resources"> <package-helper sign.package="true" /> </target>
<!-- - - - - - - - - - - - - - - - - - - - target: -package-no-sign Packages the application without signing it. - - - - - - - - - - - - - - - - - - - --> <target name="-package-no-sign" depends="-dex, -package-resources"> <package-helper sign.package="false" /> </target>
<!-- - - - - - - - - - - - - - - - - - - - - - - target: -compile-if-tested-if-test - - - - - - - - - - - - - - - - - - - - - - --> <target name="-compile-tested-if-test" if="tested.project.dir" unless="do.not.compile.again"> <subant target="compile"> <fileset dir="${tested.project.absolute.dir}" includes="build.xml" /> </subant> </target>
<!-- ======================================== target: debug Builds debug output package, provided all the necessary files are already dexed ======================================== --> <target name="debug" depends="-compile-tested-if-test, -package-debug-sign" description="Builds the application and signs it with a debug key."> <zipalign-helper in.package="${out.debug.unaligned.package}" out.package="${out.debug.package}" /> <echo>Debug Package: ${out.debug.package}</echo> </target>
<!-- - - - - - - - - - - - - - - - - - - target: -release-check - - - - - - - - - - - - - - - - - - --> <target name="-release-check"> <condition property="release.sign"> <and> <isset property="key.store" /> <isset property="key.alias" /> </and> </condition> </target>
<!-- - - - - - - - - - - - - - - - - - - target: -release-nosign - - - - - - - - - - - - - - - - - - --> <target name="-release-nosign" depends="-release-check" unless="release.sign"> <echo>No key.store and key.alias properties found in build.properties.</echo> <echo>Please sign ${out.unsigned.package} manually</echo> <echo>and run zipalign from the Android SDK tools.</echo> </target>
<!-- ====================================== target: release ====================================== --> <target name="release" depends="-package-no-sign, -release-nosign" if="release.sign" description="Builds the application. The generated apk file must be signed before it is published."> <!-- Gets passwords --> <input message="Please enter keystore password (store:${key.store}):" addproperty="key.store.password" /> <input message="Please enter password for alias '${key.alias}':" addproperty="key.alias.password" />
<!-- Signs the APK --> <echo>Signing final apk...</echo> <signjar jar="${out.unsigned.package}" signedjar="${out.unaligned.package}" keystore="${key.store}" storepass="${key.store.password}" alias="${key.alias}" keypass="${key.alias.password}" verbose="${verbose}" />
<!-- Zip aligns the APK --> <zipalign-helper in.package="${out.unaligned.package}" out.package="${out.release.package}" /> <echo>Release Package: ${out.release.package}</echo> </target>
<!-- =========================== target: install =========================== --> <target name="install" depends="debug" description="Installs/reinstalls the debug package onto a running emulator or device. If the application was previously installed, the signatures must match." > <install-helper /> </target>
<!-- - - - - - - - - - - - - - - - - - - - - - target: -uninstall-check - - - - - - - - - - - - - - - - - - - - - --> <target name="-uninstall-check"> <condition property="uninstall.run"> <isset property="manifest.package" /> </condition> </target>
<!-- - - - - - - - - - - - - - - - - - - - - - target: -uninstall-error - - - - - - - - - - - - - - - - - - - - - --> <target name="-uninstall-error" depends="-uninstall-check" unless="uninstall.run"> <echo>Unable to run 'ant uninstall', manifest.package property is not defined. </echo> </target>
<!-- ==================================== target: unistall Uninstalls the package from the default emulator/device ==================================== --> <target name="uninstall" depends="-uninstall-error" if="uninstall.run" description="Uninstalls the application from a running emulator or device."> <echo>Uninstalling ${manifest.package} from the default emulator or device...</echo> <exec executable="${adb}" failonerror="true"> <arg line="${adb.device.arg}" /> <arg value="uninstall" /> <arg value="${manifest.package}" /> </exec> </target>
<!-- ==================================== target: clean ==================================== --> <target name="clean" description="Removes output files created by other targets."> <delete dir="${out.absolute.dir}" verbose="${verbose}" /> <delete dir="${gen.absolute.dir}" verbose="${verbose}" /> </target>
<!-- Targets for code-coverage measurement purposes, invoked from external file -->
<!-- - - - - - - - - - - - - - - - - - target: -emma-instrument Emma-instruments tested project classes (compiles the tested project if necessary) and writes instrumented classes to ${instrumentation.absolute.dir}/classes - - - - - - - - - - - - - - - - - --> <target name="-emma-instrument" depends="compile"> <echo>Instrumenting classes from ${out.absolute.dir}/classes...</echo> <!-- It only instruments class files, not any external libs --> <emma enabled="true"> <instr verbosity="${verbosity}" mode="overwrite" instrpath="${out.absolute.dir}/classes" outdir="${out.absolute.dir}/classes"> </instr> <!-- TODO: exclusion filters on R*.class and allowing custom exclusion from user defined file --> </emma> </target>
<!-- - - - - - - - - - - - - - - - - - target: -dex-instrumented - - - - - - - - - - - - - - - - - --> <target name="-dex-instrumented" depends="-emma-instrument"> <dex-helper> <extra-parameters> <arg value="--no-locals" /> </extra-parameters> <external-libs> <fileset file="${emma.dir}/emma_device.jar" /> </external-libs> </dex-helper> </target>
<!-- - - - - - - - - - - - - - - - - - target: -package-with-emma Invoked from external files for code coverage purposes - - - - - - - - - - - - - - - - - --> <target name="-package-with-emma" depends="-dex-instrumented, -package-resources"> <package-helper sign.package="true"> <extra-jars> <!-- Injected from external file --> <jarfile path="${emma.dir}/emma_device.jar" /> </extra-jars> </package-helper> </target>
<!-- - - - - - - - - - - - - - - - - - target: -debug-with-emma - - - - - - - - - - - - - - - - - --> <target name="-debug-with-emma" depends="-package-with-emma"> <zipalign-helper in.package="${out.debug.unaligned.package}" out.package="${out.debug.package}" /> </target>
<!-- ====================================== target: -install-with-emma ====================================== --> <target name="-install-with-emma" depends="-debug-with-emma"> <install-helper /> </target>
<!-- End of targets for code-coverage measurement purposes -->
<!-- ====================================== target: help ====================================== --> <target name="help"> <!-- displays starts at col 13 |13 80| --> <echo>Android Ant Build. Available targets:</echo> <echo> help: Displays this help.</echo> <echo> clean: Removes output files created by other targets.</echo> <echo> compile: Compiles project's .java files into .class files.</echo> <echo> debug: Builds the application and signs it with a debug key.</echo> <echo> release: Builds the application. The generated apk file must be</echo> <echo> signed before it is published.</echo> <echo> install: Installs/reinstalls the debug package onto a running</echo> <echo> emulator or device.</echo> <echo> If the application was previously installed, the</echo> <echo> signatures must match.</echo> <echo> uninstall: Uninstalls the application from a running emulator or</echo> <echo> device.</echo> <echo> run-tests: Runs EMMA tests</echo> <echo> coverage: Runs coverage report</echo> </target> <!-- - - - - - - - - - - - - - - - - - - - - target: -set-coverage-classpath Invoking this target sets the value of extensible.classpath, which is being added to javac classpath in target 'compile' (android_rules.xml) - - - - - - - - - - - - - - - - - - - - --> <target name="-set-coverage-classpath"> <property name="extensible.classpath" location="${instrumentation.absolute.dir}/classes" /> </target>
<!-- - - - - - - - - - - - - - - - - - - - - - - - target: -install-tested-project Ensures that tested project is installed on the device before we run the tests. Used for ordinary tests, without coverage measurement - - - - - - - - - - - - - - - - - - - - - - - --> <target name="-install-tested-project"> <property name="do.not.compile.again" value="true" /> <subant target="install"> <fileset dir="${tested.project.absolute.dir}" includes="build.xml" /> </subant> </target>
<!-- ==================================== target: run-tests ==================================== --> <target name="run-tests" depends="-install-tested-project, install" description="Runs tests from the package defined in test.package property"> <run-tests-helper /> </target>
<!-- - - - - - - - - - - - - - - - - target: -install-instrumented - - - - - - - - - - - - - - - - --> <target name="-install-instrumented"> <property name="do.not.compile.again" value="true" /> <subant target="-install-with-emma"> <property name="out.absolute.dir" value="${instrumentation.absolute.dir}" /> <fileset dir="${tested.project.absolute.dir}" includes="build.xml" /> </subant> </target>
<!-- =============================================== target: coverage =============================================== --> <target name="coverage" depends="-set-coverage-classpath, -install-instrumented, install" description="Runs the tests against the instrumented code and generates code coverage report"> <run-tests-helper emma.enabled="true"> <extra-instrument-args> <arg value="-e" /> <arg value="coverageFile" /> <arg value="${emma.dump.file}" /> </extra-instrument-args> </run-tests-helper> <echo>Downloading coverage file into project directory...</echo> <exec executable="${adb}" failonerror="true"> <arg value="pull" /> <arg value="${emma.dump.file}" /> <arg value="coverage.ec" /> </exec> <echo>Extracting coverage report...</echo> <emma> <report sourcepath="${tested.project.absolute.dir}/${source.dir}" verbosity="${verbosity}"> <!-- TODO: report.dir or something like should be introduced if necessary --> <infileset dir="."> <include name="coverage.ec" /> <include name="coverage.em" /> </infileset> <!-- TODO: reports in other, indicated by user formats --> <html outfile="coverage.html" /> </report> </emma> <echo>Cleaning up temporary files...</echo> <delete dir="${instrumentation.absolute.dir}" /> <delete file="coverage.ec" /> <delete file="coverage.em" /> <echo>Saving the report file in ${basedir}/coverage/coverage.html</echo> </target>
</project>
The other non-emma test targets are not added yet. The main idea is to have one build file that can be used in the app source and test source folders both through the IDE and later on through a continuous build server.
QXRWH6NHQNH2 just to make sure I get listed on Technorati. Have a nice xmas.
Before I being this, some background. Sometimes intelligent gifted people are not the easiest to interface with. Dave Winer certainly could be said to be the Frank Zappa of the RSS user community at times. So when you find an aha moment from dave winer explained by himself in an easy non pressure language its a real find.
Dave Winer recently started using an Android device with OS 1.5 and wanted to know how to do screen capture form a user perspective that means not installing something like the Android SDK or even probably installing something else. The thread he comments in is here.
The Gem is the last comment in the thread in that Dave Winer challenges all developers to look past our feedback systems that are developer centric and adopt a more user friendly approach. Let me explain, you know that physical thing called the Apple retail store? ever notice how there i snot a single install of any developer bug trackers there? Ever wonder why?
That is one of the reasons why you should use something like DroidDrop to remotely log the application problem as you do not want extra step sin consumer application feedback. the more times you can step into the consumers shoe sand think like them the better the consumer application.
Welcome to the Android User community Dave Winer..I forgot to mention DW’s Droid user blog is here.
I have 8 Google Wave invites. To get one state what you are working on and your gmail account address as a comment to this post. I apologize in advance that I can only awadr 8 as I know that I will get many responses from hard working android developers. I only ask that if invited that you be willing to use your invites to invite more Android developers. I will send them out sometime around Friday evening.
o I am finishing up my template creation for the AndCooper Android Application Build Tool so that I can submit another TDD bgu fix for the Android SDK and finalize up AndCoooper 0.1. My performance TestCase looks like this before I transform it into ctl template language constructs:
package com.mobilebytes.mymapview;
import android.test.AndroidTestCase;
import android.test.PerformanceTestCase;
/**
* This PerformanceTest TestCase class is
* launched with
* adb shell am instrument -w -e perf true ${application-package}.tests/android.test.InstrumentationTestRunner
*/
public class PerformanceTest extends AndroidTestCase implements
PerformanceTestCase{
@Override
public boolean isPerformanceOnly() {
// TODO Auto-generated method stub
return true;
}
@Override
public int startPerformance(Intermediates intermediates) {
intermediates.startTiming(true);
// TODO Auto-generated method stub
intermediates.finishTiming(true);
return 0;
}
}
And my ant target looks like this:
<target name="tests.performance" depends="reinstall" description="tests perforrmance">
<echo>Building and installing tests..</echo>
<exec executable="ant" failonerror="true">
<arg value="-f" />
<arg value="tests/build.xml" />
<arg value="reinstall"/>
</exec>
<mkdir dir="${basedir}/log" />
<exec executable="${adb}">
<arg value="shell" />
<arg value="am" />
<arg value="instrument" />
<arg value="-w" />
<arg value="-e" />
<arg value="perf"/>
<arg value="true"/>
<arg value="${application-package}.tests/android.test.InstrumentationTestRunner" />
</exec>
</target>
what is the difference between this and Monkey UI testing? Monkey UI sends random UI events, you can control the percentage per UI event category. Performance TestCase would be for when you have narrowed down some user cases that need optimization and thus you are setting up timing test which may focus on UI events for that user case and other events testing of that user case.
MobileBytes 