[
https://issues.apache.org/jira/browse/OAK-1442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13908478#comment-13908478
]
Tommaso Teofili commented on OAK-1442:
--------------------------------------
I see your point, main reason for this is avoiding having to re-pack the ~4MBs
brought by Lucene dependencies in two different places.
Any other smarter ideas? Would it sound better to have one or two separate
(optional) oak-search-osgi bundles bringing those dependencies and let
oak-lucene / oak-solr bundles be slimmer :-) ?
> Let oak-lucene export its embedded Lucene dependencies
> ------------------------------------------------------
>
> Key: OAK-1442
> URL: https://issues.apache.org/jira/browse/OAK-1442
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: oak-lucene
> Affects Versions: 0.16
> Reporter: Tommaso Teofili
> Assignee: Tommaso Teofili
> Fix For: 0.17.1
>
>
> Oak Lucene module embeds lucene-core and lucene-analyzers-common as they are
> not available as OSGi ready packages (see LUCENE-3167) therefore it would be
> useful to have such dependencies exposed (via <_exportcontents> directive) so
> that they can be used by Oak Solr module in OSGi deployments.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
