Archive for February, 2010

More iPhone UI Goodness

Posted: February 28, 2010 in Android
Tags: ,

Title bar flashing was removed by sticking:

android:theme="@android:style/Theme.NoTitleBar"

..in the first activity. Music was added to first activity(sorry about no sound in the video..still figuring out gtk-recordmyDesktop and my soundcard):

 final MediaPlayer mp = MediaPlayer.create(Splash3d.this, R.raw.welcome2jungle_remix);
         try {
			mp.prepare();
		} catch (IllegalStateException e) {
			// TODO Auto-generated catch block
			e.printStackTrace();
		} catch (IOException e) {
			// TODO Auto-generated catch block
			e.printStackTrace();
		}
         mp.start();

What is next is to override the transition to the next activity using overridePendingTransition() which is an Android 2.0 feature. Prior to Android 2.0 you would do it manually in each activity being triggered by a hander timer.

Advertisements

The general idea is as I work through polishing certain UI coding elements to do a tutorial series on making Android Apps Look/feel like iPhone Applications. Right now I have the 3D Splash screen implemented:

Basically, in frame layouts everything is visible but you can modify  that on-the fly and than use matrix and camera to manipulate the ImageView.

Now, its change from a click handler to rotating it based on a time period unit than after that time period expires sending intent to change to next activity. Than put some ImageView manipulation magic in for reflection and shadows, which means translating all the layout XML parameters to java code setting them as that is the only way to grab the ImageView correctly to set reflection and shadows.

I am using popularity to decide if the tutorial series is worth it. Thus far it seems like there may be enough interest.

Reblog this post [with Zemanta]

UI Goodness

Posted: February 26, 2010 in Android
Tags:

This what the average Android Developer does in form of an UI:

Now, guess what I am going to implement on this to bring it up to iPhone UI quality? It involves breaking a bad android programming habit…stay tunned.

One thing that is the same in skills and processes with the effort to get sales in Android Market is something that may at first glance might not seem related,androd development consulting customers.
You have the same process of analyzing where that target audience might look on the web and attempting to grab that audience. Suffice it to say that free demos and free videos are like the resume to get that Android Application Review site to review your application and thus that review becomes a marketing tool to get new customers.

Just like the recruiters on Linkedin, you have to avoid spending time on those groups that are not tangential towards your goals of getting customers. In the Android Market case, coverage by a non android application review site will only matter if the audience is directly using Android devices in high numbers.

But what free applications? It has to be a free android application that attracts an android application review site to review said application. Top sellers at this time seem to be Games, Entertainment, Utilities, and feature rich AppWidgets.

The free applications I am finishing are at this time an AnimatedWidget, a Feeds Application, a game, and a file browser application. notice that I did not state free android applications with someone else’s brand on it? At this point you will want your brand on it and that brand pointing to your stuff.

Reblog this post [with Zemanta]

Home Replacement Application

Posted: February 19, 2010 in Android
Tags:
Android Market
Image via Wikipedia

I have a collection of Android application ideas on my hard drive but Home Replacement applicatiosns seem to be the top sellers in the Android Market for paid applications.

There is of course dealing with the private APIs still associated with the Home application than how do I sell the less functional one? Maybe I could sell the less functional 0one as Retro Android HomeScreen? Than there is the aspect of how do I top the HomeScreen Applications already out there?

But, its the types of programming puzzles I want to solve that seem interesting to me from developing a theme API so HomeScreen assets can be stored on the SDCard to view optimization, etc. Plus, I want to push the HomeScreen UI into another direction.

Reblog this post [with Zemanta]

Custom Title

Posted: February 18, 2010 in Android

Playing around with custom titles:

Notice back button actin like iPhone.

Testing Tip 102

Posted: February 15, 2010 in Android
Tags:

If you have not done already move all your trace files and hprof dump file programming commands to your testcases class. why?

1. Because its called in your Testcase you no longer have to comment it out to publish your application.

2. You can implement a special ant task that triggers or runs that TestCase and dumps the trace and hprof files in your coverage or performance folder for viewing and analysis.

3. If you cannot find the memory miss-use you would be attempting some heavy Monkey UI test runs with -hprof enabled anyway thus there really i snot another case where you would actually need full hprof on the entire application and all its functions.

Android PMD 5

Posted: February 12, 2010 in Android
Tags: ,

PMD 5 comes with some new additions to the Android Rules and a nice new features in that you can define a rulest and stick outside the pmd.jar unlike PMD 4. Thus for an ANT target you have:

 <!-- PMD -->
			    <target name="pmd" >
			    
                           <pmd rulesetfiles="config/androidrules.xml">
			    	            <auxclasspath>
			    	                <pathelement location="${sdk-android-jar}"/>
			    	                <pathelement location="${out.classes.absolute.dir}" />
			    	                <fileset dir="libs">
			    	                    <include name="*.jar" />
			    	                </fileset>
			    	            </auxclasspath>
			    	            <formatter type="xml" toFile="reports/pmd.xml"/>
			    	            <!-- <ruleset>rulesets/java/android.xml</ruleset> -->
			    	            <fileset dir="${source-folder}" includes="**/*.java" />
			    	        </pmd>
			    	    <xslt basedir="reports" destdir="reports"
			    		style="config/reportconfig/andcooper.pmd.xsl">
			    		<param name="project" expression="${project}"/>
			    		<param name="today" expression="${today}"/>  
			    		<param name="rulesets" expression="android"/>
			    		<mapper type="glob" from="pmd.xml" to="pmd.html"/>
                    </xslt>
			    	
					 
					   <echo>pmd report generated and transformed to html</echo>
				</target>
	

Application JavaDoc

Posted: February 10, 2010 in Android
Tags: , , ,

There are some javadoc errors that I see when developers attempt to produce javadoc for an Android application project. One, not specifying the android.jar as a classpath parameter and the second is not specifying what Androdi SDK version in th e footer some place:

<target name="javadoc">
	
		<javadoc sourcepathref="javadoc.source" destdir="javadocs" overview="src/overview.html" classpath="${sdk-android-jar}" private="true" windowtitle="${taglets.windowtitle}" additionalparam="">
					<!-- Use a nice documentation title -->
					   <doctitle>
					     AndroidAppANTBuild&lt;/br&gt;
					     API Specification
					   </doctitle>
					     	 <!-- Create a header that contains the taglets logo -->
					     	   <!-- Note the use of the {@docRoot} tag to link to the logo -->
					     	   <header>
					     	     &lt;img
					     	       src="{@docRoot}/resources/logo.png" 
					     	       width="88" height="40" border="0"
					     	     &gt;
					     	   </header>
					<!-- Same for the footer -->
					   <footer>
					     &lt;img 
					       src="{@docRoot}/resources/logo.png" 
					       width="88" height="40"
					     &gt;
					   </footer>
					   <!-- Include a timestamp at the bottom of the docu generated -->
					   <!-- Note the use of ${timestamp} which was created by the -->
					   <!-- <tstamp> task at the start of this target -->
					   <bottom>
					     &lt;p align="right"&gt;
					       &lt;font class="NavBarFont1" size="-1"&gt;
					   	     Android SDK Verion ${sdk.version}&lt;br&gt;
					         ANdroidAppANTBuild&lt;br&gt;
					         API Spec&lt;br&gt;
					         ${TSTAMP} ${DSTAMP}
					       &lt;/font&gt;
					     &lt;/p&gt;
					   </bottom>
			
			</javadoc>
</target>

Remember, there is no separate javadoc for the SDK online so you really can not use a link parameter and thus identifying the SDK version in footer helps.

Reblog this post [with Zemanta]

ANT Build file

Posted: February 7, 2010 in Uncategorized

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.