Daniel Passos schrieb am 10.07.2013 18:00:
Hey Marc,
Thanks for your email
with pleasure :)
Marc Sluiter wrote:
> The problem with "Could not find tool 'aapt'" was solved by
updating the
> android-maven-plugin to version 3.6, so also no need to create a link to it. But
> then it was missing the platform version, so my pom looks like this now:
>
> <plugin>
> <groupId>com.jayway.maven.plugins.android.generation2</groupId>
> <artifactId>android-maven-plugin</artifactId>
> <version>3.6.0</version>
> <configuration>
> <sdk>
> <platform>17</platform>
> </sdk>
> <undeployBeforeDeploy>true</undeployBeforeDeploy>
> </configuration>
> <extensions>true</extensions>
> </plugin>
>
> I also had to increase the version number of the support lib:
>
> <dependency>
> <groupId>android.support</groupId>
> <artifactId>compatibility-v4</artifactId>
> <version>13</version>
> </dependency>
>
> Finally I had to add 2 lines in proguard.cfg in order to let maven build
> successfully:
>
> -dontwarn android.support.**
> -dontwarn com.google.android.gms.**
Wdyt about send a PR for this? :)
No problem, can do it tomorrow!
Will 1 PR be fine, or do you prefer to split the 3 changes?
Marc