Package naming is largely irrelevant, except there are some major conventions. For example. the Java API is largely under java.
. The real purpose is to avoid conflict with other code.
The primary impact package naming has is on visibility. Protected members, for example, are available to the same package (and subclasses), but not to code in other packages.
For example, on my phone, code seems to be primarily in com
:
com.areacode.drop7
com.google.android.apps.
com.meebo.
but some is in org
(mostly open source stuff):
org.connectbot
org.npr.android.news
Some discussion on Wikipedia:
http://en.wikipedia.org/wiki/Java_package#Package_naming_conventions
As long as your company name (and app name) is in the package name, you should be fine.
Eclipse has provisions for linking multiple projects together as libraries. If you are using ant for your build process, you can do the inclusion there. There's not a real concept of a "library" (a JAR file in J2SE) that I'm aware of. Actual JAR files (as compiled for J2SE) need to be cross-compiled to the Android format (DEX).