search

yuchen931201 / maven-android-plugin

Automatically exported from code.google.com/p/maven-android-plugin
0 stars 0 forks source link

Infer android.sdk.platform from existing config files #20

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Can we look at the "uses-sdk" tag in AndroidManifest.xml, and from that 
understand what the value should be for android.sdk.platform, if the user 
has not set it?

Then they would really only need to configure one thing in one place:
1. android.sdk.path in pom.xml
2. platform a.k.a. uses-sdk in AndroidManifest.xml

The mapping would look like this with a normal Android SDK 1.5 from Google:

Android SDK 1.0 = 1
Android SDK 1.1 = 2
Android SDK 1.5 = 3

What version of maven-android-plugin are you using?
2.0.0-alpha3

Original issue reported on code.google.com by hugo.josefson.old@gmail.com on 17 Jun 2009 at 3:54

GoogleCodeExporter commented 9 years ago 
Using sdklib from the Android SDK, we should be able to parse 
default.properties,
which is apparently where platform information for the project is read by the 
ADT
plugin in Eclipse.

See this thread on Android Discuss for details from Xavier Ducrohet at Google:
http://groups.google.com/group/android-discuss/browse_thread/thread/c79df0ea6bda
013f

Original comment by hugo.josefson.old@gmail.com on 17 Jul 2009 at 9:48

GoogleCodeExporter commented 9 years ago 
sdklib will not help you parse the .properties file, but that's easy to do 
(it's a
basic property file). What sdklib will help you is resolve the value of the 
"target"
property so that you can figure out the path to android.jar (and possibly other 
jar
files) needed for the compilation. A good example is the custom Ant task that 
does
just that (except the properties are imported automatically in build.xml). See
development/tools/anttasks/src/com/android/ant/SetupTask.java

Original comment by xav%andr...@gtempaccount.com on 17 Jul 2009 at 10:45

GoogleCodeExporter commented 9 years ago

Original comment by hugo.josefson.old@gmail.com on 17 Dec 2009 at 8:24

GoogleCodeExporter commented 9 years ago

Original comment by mosa...@gmail.com on 22 May 2012 at 5:30

GoogleCodeExporter commented 9 years ago 
We are no longer using the issue tracking system on Google Code. Please refile 
this issue on https://github.com/jayway/maven-android-plugin/issues if you 
still have this problem with the latest release of the Android Maven Plugin

Original comment by mosa...@gmail.com on 19 May 2014 at 4:18