[
https://issues.apache.org/jira/browse/TIKA-340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated TIKA-340:
-------------------------------
Attachment: osgi-logging.patch
OK, you have a better view of the best practices for logging with OSGi. See the
attached osgi-logging.patch for a quick and dirty experiment of what we could
do if we did want to directly use the OSGi log service.
If the OSGi runtimes already unpack the bundle jar, then I have no problem with
the embedded jars. Could we even avoid inlining the tika-core and tika-parsers
jars, or is that something that's needed for the Export-Package rules to work?
If the latter, can we exclude org.apache.tika.parser subpackages from being
exported so that only tika-core gets inlined?
Let's take the size issue to tika-...@.
> 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: osgi-logging.patch, 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.
