[
https://issues.apache.org/jira/browse/TIKA-340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12784798#action_12784798
]
Felix Meschberger commented on TIKA-340:
----------------------------------------
Re: logging:
Yes, that might be true -- still there is some API to implement and if you
mplement logging based on LogService you loose all the log categories
previously used because the OSGi LogService does not have such a concept.
Also, if you want to reuse the library in non-OSGi environments using the
LogService will not work and create an OSGi dependency.
Re: size:
I knew there is some activity in this area. Thanks for the pointer.
Re: inlining
Why is the double compression troublesome ?
What the OSGI framework actually does, is unpacking the bundle jar. Thus
embedded libaries are unpacked into jar files, that is unpacking is not
recursive. Then the regaluar classes are loaded regularly while the embedded
JAR files are loaded as JAR URLs.
Thus in the end, it might even be better to embed the libraries than to inline
them.
But this decision depends on whether you want to use the result of the build in
a non-OSGi environment or not. If you only target OSGi frameworks, then I would
go for embedded libraries. Otherwise I would go for inlined libraries at the
expense of 20% of the size of the resulting JAR file.
> 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.
