Library Project does the manifest file merge?

I am thinking of creating a core application library (a library project with all the logic), a free version)and a full version that use this library.

As I understand some things in the manifest do not merge down like permissions and activities, does the version code merge? Could I put a single version code in the library to apply to both the free and paid versions?

The sec开发者_运维技巧ond question is, my current application (The one I will turn into an Android library) depends on a library, therefore if I make it a library, as I understand it, you cannot have a library inherit from a library. How do I get around this?

AndroidManifest.xml merging is supported in version 20 of the ADT tools:

"Automatic merging of library project manifest files into the including project's manifest. Enable with the manifestmerger.enabled property."

http://tools.android.com/download/adt-20-preview

You will need version 20.0.3 or newer to get it to work within Eclipse.

Release notes for ADT 21 preview has this comment:

"Fixed manifest merger to properly adapt library classes in the merged manifest."

Not sure what this means but may be worth checking out if you are having merge issues.

THIS ANSWER WAS CORRECT FOR EARLIER VERSIONS OF THE ANDROID SDK BUT IS NOW OBSOLETE. SEE Hayes's ANSWER BELOW FOR MORE UP-TO-DATE INFO.

1. The manifest file for a library project is almost totally not used. The only part that's necessary is the manifest element with a package attribute. I believe the rest of the manifest for a library project is ignored.

2. The android tools released in Sept 2010 do support a library project referencing a library project. The docs state otherwise, but I'm pretty sure they are out-of-date.

Manifests are not merged, but I recall there's an include statement in Android XMLs.

Arbitrary-level library dependence was introduced in a recent version of Android SDK IIRC.