Would it not be reasonable to split the single big android.jar into multiple jar files where all of the classes that could be used in a standard Java application running with a vanilla J2SE appear in a subset of the jar files, along the lines of an API jar and and a couple of implementation jar's.
This would facilitate testing, and also allow development of libraries that could be used for example in a standard Java web application and in an Android mobile application. As a specific example, a library that encapsulates the interaction with some web service may define Java entity classes, and for Android RPC these may need to implement android.os.Parcelable. This drags in andorid.os.Parcel which seems to be intimately connected to the Android platform, and yet this is just a serialization scheme equally applicable to a web application... Would appreciate any discussion to clarify my thinking (seasoned in Java, but still a bit green in the Android world)... -- 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

