[
https://issues.apache.org/jira/browse/TIKA-340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12784761#action_12784761
]
Jukka Zitting commented on TIKA-340:
------------------------------------
Re: logging; AFAIUI using the OSGi log service directly makes it possible for
the log backend to sort out log messages based on the bundle from which they
originated. That doesn't seem possible if we just depend on a support bundle
that exposes the commons-logging API.
Re: size; Yep, that's another story. See
http://jukkaz.wordpress.com/2009/10/16/putting-poi-on-a-diet/ for the gory
details.
Re: inlining; The double compression of embedded jars explains the size
difference you're seeing. That double compression seems a bit troublesome to me
given the large number of non-class resources (PDF font mapping data, OOXML
schemas, etc.) we have there. Ideally the classloader should be able to load
such resources on demand without having to uncompress the entire archive. But I
guess OSGi runtimes may already avoid that problem in similar ways as servlet
containers do with embedded jars in WEB-INF/lib.
> 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-2.patch, 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 missing.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
