Thanks for committing.
> Would you mind if we rather called the package tika-bundle or tika-osgi instead of tika-full?
Not at all ...
> Some further improvements would be to automatically wire all logging to the OSGi log service
Well the bundle as it stands currently has imports for Log4J and Commons Logging. Both APIs are generally available from some logging support bundle, for example the Sling Log Service implementation or PAX logging. I am not sure, whether it is worth it to try to converge the logging approaches into OSGi LogService in the Tika Bundle itself.
> some of the dependencies to be inlined
Generally I came to like to embed JAR files. This makes it a lot easier to inspect the JAR files and AFAICT has no drawbacks on usability in an OSGi environment. I have inline one JAR file because I had to exclude an incomplete org.w3c.dom package, which would have caused resolution issues.
OTOH if you would deem the jarfile useful in general, that is non-OSGi, environments, it would probably make perfect sense to inline the embedded libraries. In this case, though, the name of the library should probably not contain the words "osgi" or "bundle". WDYT ?