[
https://issues.apache.org/jira/browse/OAK-1442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13910804#comment-13910804
]
Jukka Zitting commented on OAK-1442:
------------------------------------
bq. Bundling oak-lucene and oak-solr-* together (e.g. in oak-fulltext) would
give the advantage of avoiding having to rebundle and distribute Lucene / Solr
bundles (which is a bit tricky)
As said above, this is what I'd go for.
bq. on the other hand it'd provide everything also to users wanting to just use
one of the two index providers.
People who use Solr would in any case need the Lucene dependencies (otherwise
we wouldn't need this issue), so this drawback would only impact deployments
that use Lucene but not Solr. If the cost of including Solr is too high, I'd
put those dependencies in a fragment bundle (or two, for the remote/embedded
cases) that attaches to {{oak-fulltext}}. This approach would give us the best
of both worlds: no extra cost of unused dependencies, and no unnecessarily
exposed external packages.
> 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
>
> Attachments: OAK-1442.patch
>
>
> 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)
