Exclude all except jar dependcies from proguard -injar parameters to solve https://code.google.com/p/maven-android-plugin/issues/detail?id=319
Upgraded AndroidSdk to use path and platform utilities from sdklib

Searching for paths of tools and locating the installed Android platforms now done using sdklib. This should hopefully make the plugin more resilient to directory structure changes like we had in tools 22.
Removed console logging put in during testing
added support for multiple source folders
Added support for Uses-sdk changes by configuration.
Modified manifest and manifest updating process.
Moved UsesSdk into configuration to have it in a more meaningful place.
Final clean up before pull request.
Removed some info logs.
removed debug mode command line flag since it no longer exists for aapt
updated to support sdk v 22.0 but also fall back correctly
Merge branch 'sdklib' of https://github.com/nicstrong/maven-android-plugin into sdklib
made android sdk platform/api level mandatory including for ndk based projects, this is correcter and better than any other fixes I tried, also updated the tests to continue to work
Merge branch 'pull_fix_proguard-injar' of https://github.com/tprochazka/maven-android-plugin into 191
adding platform 17
updated to r22 of the sdk
Merge pull request #209 from tuenti/support-uses-sdk-tag

Support uses sdk tag
Merge branch 'master' of https://github.com/kedzie/maven-android-plugin into 208
code style fixes
platform tool and level commissioning