[
https://issues.apache.org/jira/browse/TIKA-340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12785204#action_12785204
]
Felix Meschberger edited comment on TIKA-340 at 12/3/09 7:26 AM:
-----------------------------------------------------------------
> Could we even avoid inlining the tika-core and tika-parsers jars
Yes, I will create a new issue with patch.
was (Author: fmeschbe):
> Could we even avoid inlining the tika-core and tika-parsers jars
Partially and theoretically, yes.
Unfortunately, the <Export-Package> element causes the exported packages to be
inlined. So whatever we export is being inlined.
Now, what to export: I cannot really tell.... Let's take this to tika-dev@, too
(and a new issue)
> 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.
