On Mon, Feb 7, 2011 at 9:30 AM, Pepijn Van Eeckhoudt <[email protected]> wrote: > I guess you're refering to the third-party > sdk addons preinstalled system libraries. The example I'm referring to from > google is a bit different though. If you install it you essentially get an > unzipped library project, documentation and sample code which you can then > start using.
Ah, sorry, I missed that in your original post. > I've been testing with a repository.xml containing my sdk:extra in the > meantime and it works; I just have concerns that it might break in some > future SDK release as there is no documentation on this besides the code. Eventually, the tools project will hopefully document it. http://tools.android.com/ > In > the end, this is still the same as a zipped library project with the added > benefit that the SDK manager handles checking for updates. Agreed. That would be nice. If you're a Maven-ite, there's also the possibility of distributing that way, though I usually think of that being for internal stuff or open source stuff. I'm not a Maven user, so my experience with it is minuscule. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy _The Busy Coder's Guide to *Advanced* Android Development_ Version 1.9 Available! -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
