Closed GoogleCodeExporter closed 9 years ago
Implementation note:
unpacking in temporary or configured directory (if not already there),
using from there.
Original comment by hugo.josefson.old@gmail.com
on 7 Jun 2009 at 8:57
Original comment by hugo.josefson.old@gmail.com
on 7 Jun 2009 at 9:45
Down-prioritizing for now.
Please place a comment here if you want it implemented, and I'll up-prioritize
it
again :)
Original comment by hugo.josefson.old@gmail.com
on 15 Jul 2009 at 9:08
there is already a tool to do this:
http://github.com/mosabua/maven-android-sdk-deployer
you first install the android sdk, then get it to grab the relevant packages.
the deployer goes through all the packages, grabs the jars and pushes them into
your
local maven repo.
also provides a means to deploy to a shared repository too.
Original comment by jason.dwyer@gmail.com
on 20 Dec 2009 at 2:24
Ideally the deployer tool Jason mentions could do the whole SDK install. The
only
problem is that there is no legal way to download the SDK automatically (click
through
EULA...) so we would have to replicate the flow through a browser. Thats too
much
pain. Maybe we should get the OHSA to do some sort of distribution license like
Sun
used to have to the JDK before they opensourced it..
Original comment by mosa...@gmail.com
on 30 Jan 2010 at 12:11
I second this issue. It would make clean, reproducable builds much easier.
I wonder what's the issue about the license - Android is Apache licensed which
certainly allows redistribution, and the SDK classes are already in Maven
central (although Android 4.1 only).
Original comment by andreas....@gmail.com
on 14 Jun 2013 at 2:08
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
Original issue reported on code.google.com by
hugo.josefson.old@gmail.com
on 7 Jun 2009 at 8:56