tika-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Felix Meschberger (JIRA)" <j...@apache.org>
Subject [jira] Commented: (TIKA-340) Provide full Tika bundle
Date Wed, 02 Dec 2009 06:10:20 GMT

    [ https://issues.apache.org/jira/browse/TIKA-340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12784648#action_12784648

Felix Meschberger commented on TIKA-340:

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

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

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 ?

> Provide full Tika bundle
> ------------------------
>                 Key: TIKA-340
>                 URL: https://issues.apache.org/jira/browse/TIKA-340
>             Project: Tika
>          Issue Type: New Feature
>          Components: packaging
>    Affects Versions: 0.5
>            Reporter: Felix Meschberger
>            Assignee: Jukka Zitting
>             Fix For: 0.6
>         Attachments: TIKA-340.patch
> To easily deploy Tika and especially the Tika parsers, it would be convenient to have
an almost complete bundle consisting of Tika Core, Tika Parsers as well as the most important
parser dependencies. Any remaining dependencies not included with the bundle should be declared
as optional import to not fail bundle resolution if one or the other (or all) import(s) is

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message