updated maven pom to use repo.jenkins-ci.org repository
Refactors common state into a context.

This creates a new AndroidEmulatorContext that encapsulates a lot of commonly
used state, so that we don't have to pass around a bajillion variables.  It also
has some handy utilities to DRY the code a little.
Allow user to specify an abi to use for the emulator

For some versions of Android there is more than one available
system image / ABI. When more than one image is installed,
the user needs to specify which version is to be used.
Merge pull request #12 from jberkel/master

[FIXED JENKINS-13906] Allow user to specify target abi / system image
[JENKINS-11973] Option for emulators in $WORKSPACE

This adds a global option that essentially does
ANDROID_SDK_HOME=$WORKSPACE, causing emulators to be put into
$WORKSPACE/.android.

This allows you to run concurrent jobs on the same slave, and to run the
same emulator config from two different jobs on the same slave. It also
makes the emulators more isolated and allows you to clean-slate the
emulators by wiping out the workspace.
Fix parsing of recent SDK revision strings

The most recent Android SDK uses a major/minor/patch version string like
"20.0.1", this changeset adds support for this.
Improved regex
Merge pull request #14 from jberkel/master

[FIXED JENKINS-14497] Fix parsing of recent SDK revision strings.
Merge pull request #13 from jorgenpt/workspace-local-android-images

[FIXED JENKINS-11973] Allow emulators to be stored in $WORKSPACE.
[maven-release-plugin] prepare release android-emulator-2.3
[maven-release-plugin] prepare for next development iteration
[JENKINS-15097] Deal with crazy android version strings
Merge pull request #15 from recampbell/master

[JENKINS-15097] Deal with crazy android version strings
Add support for Android 4.1.
[maven-release-plugin] prepare release android-emulator-2.4
[maven-release-plugin] prepare for next development iteration
In general Launcher may not be serializable.

By the time the closure is executing, you are already on the target
platform, so you'd be better off just asking your JVM
(File.separatorChar, etc) about the current platform.
'isUnix' flag mostly unneeded.

In relation to a531f90453e25378efc5a1b1e15b55a99c25f709, I noticed that
the way the 'isUnix' flag is used is mostly redundant. It's computed by
the master and then passed with a closure to be exected on the slave.

But once your code starts to execute on the slave, its JVM already knows
what platform it is running on. So it's more concise and faster not to
pass around this flag from the master.

Similarly, when a method signature returns a File, like
Utils.getHomeDirectory(), then you are by definition already executing
on the target JVM, so these functions shouldn't take the 'isUnix'
parameter. It's concise, faster, and less error prone to just let this
function computes whether it's running on an Unix or not.

This commit eliminates those redundant uses of the 'isUnix' flag from
the signature.

I don't know if other plugins started depending on these signatures,
and/or if you'd like to maintain API compatibility, so I'm sending this
in as a pull request. Please feel free to disregard if that is the case.
Merge pull request #16 from kohsuke/master

Get rid of the redundant 'isUnix' flag.
Automatically install SDK if required from ProjectPrerequisitesInstaller.

Previously, the SDK was only installed if an emulator was being started.
But often you may want to build an app in one job, then run the emulator in another.