Monday, February 7, 2011

Re: [android-developers] Library packaging best practices

On Mon, Feb 7, 2011 at 6:00 AM, Pepijn Van Eeckhoudt
<pepijn@vaneeckhoudt.net> wrote:
>  What is the recommended way of distributing a reusable library (i.e., jar
> file, assets, documentation, sample code)?

ZIP file, backed by a GitHub repo or the equivalent.

> One possibility I'm considering is an sdk extra (the same way for instance
> the google market_licensing library is made available in SDK manager. Is
> this a supported mechanism or should this not be used?

Depends. Are you making your own phone?

> Are there any other, possibly better, alternatives besides distributing a
> zipped library project?

You could supply it on clay tablets, using cuneiform. However, since I
don't think the zero had been invented yet, you'll have to choose two
characters to represent 0 and 1 for the bits.

Hey, you asked for "other, possibly better", which leaves open the
possibility of "other, completely moronic"... :-)

--
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 android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

0 Comments:

Post a Comment

Subscribe to Post Comments [Atom]

<< Home


Real Estate