Feature choose which version of the build tools to use

[Shusshu]

This PR adds the ability to choose which the version of the build tools we want to use.

<sdk>
     <platform>22</platform>
<!--        <buildTools>19.0.0</buildTools> -->
</sdk>

A) When a user does not set the build tools it will behaves exactly as it is now.

B) If the user decide to put a build tool it will try to find that version of the build tools or throw an exception.
I prefer this approach over the one where if it cannot find the build tools specified it will take the latest one... I assume if I user set that value there must be a reason and we don't want to use another build tool version. (With a CI you can be sure your PC and the CI uses the same build tools)

Note about the code:
When we receive an AndroidTarget for version 19 from the google lib it gives us the correct target but the target will always try to find the latest build tools.
So I decided to put a seperate parameter for the build tools (same as gradle btw)

[Shusshu]

@simpligility/android-maven-plugins-core-committers +1 or merge :) I've added some unit tests and tested it on a project with different configuration

[Shusshu]

If anyone can help out with travis that would be cool

[WonderCsabo]

You have to install build tools 22 in Travis in this line. Just adding build-tools-22.0.1 should work.

[Shusshu]

Already tried that

[WonderCsabo]

And what happened? Does it install the SDK?

Is this working for you locally?

[Shusshu]

Nop it times out it seems... I don't have travis locally. I thought it was
only in the cloud.

[WonderCsabo]

I meant the PR works for on the local machine? With your local SDK setup, no travis.

[Shusshu]

Yes ofc only travis is not working.

[william-ferguson-au]

+1

[WonderCsabo]

I managed to build with the built-in Travis Android support. But it is reproducing the same failures. I do not know why it cannot find build tools 22. 😖

[Shusshu]

@malachid last time you worked on travis right?

[mosabua]

If its building locally we should merge and then look at travis. I already had to disable the IT test run there since it kept failing even though it worked locally. Travis supposedly now has native android support but we have not migrated to that yet (or even tried).

[WonderCsabo]

@mosabua i already tried Travis, but i had to comment out emulator and NDK. Should i send a PR and try to make them work?

[Shusshu]

yes please

Benoit Billington

[mosabua]

@WonderCsabo anything is better than the simple install we run now .. so yes please.

[WonderCsabo]

OK, i am looking at it.