[
https://issues.apache.org/jira/browse/OAK-1475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13915799#comment-13915799
]
Tommaso Teofili commented on OAK-1475:
--------------------------------------
Quick update on this issue.
I tried the described approach and while it could be possible to make
oak-solr-* fragmens of oak-lucene (it took a bit of configuration tricks) we
wouldn't have proper OSGi services exposed (as fragments don't have activators)
that later may get picked up by the WhiteboardIndex(Editor)Provider.
This problem can be mitigated by merging oak-solr-* bundles in a single
fragment bundle with oak-lucene as the fragment-host and create an
oak-solr-osgi bundle which imports the oak-solr-* exported packages and just
exposes the relevant OSGi services. This option has the advantage that we don't
have to explicitly wrap and export Solr classes in a dedicated bundle, as the
Solr stuff would be embedded in oak-solr and the only exported classes (to be
imported by oak-solr-osgi) would be the ones of oak-solr-* which we manage
(with proper semantic versioning).
An alternative solution proposed by [~jukkaz] is to merge oak-lucene and
oak-solr-* in oak-fulltext and let just the Solr dependencies be packaged as a
fragment of oak-fulltext.
> Make Oak Solr bundle a fragment of Oak Lucene
> ---------------------------------------------
>
> Key: OAK-1475
> URL: https://issues.apache.org/jira/browse/OAK-1475
> Project: Jackrabbit Oak
> Issue Type: Wish
> Components: oak-lucene, oak-solr
> Affects Versions: 0.16
> Reporter: Tommaso Teofili
> Assignee: Tommaso Teofili
> Fix For: 0.18
>
>
> As suggested in OAK-1442 it'd be useful to avoid duplicating Lucene
> dependencies used by Oak Solr and therefore that should be a fragment of
> oak-lucene as host.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
