[
https://issues.apache.org/jira/browse/OAK-438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13495223#comment-13495223
]
Jukka Zitting commented on OAK-438:
-----------------------------------
Even though I dislike splitting stuff over too many components, in this case
the cleanest approach would seem to be to create a separate {{oak-lucene}}
component that contains the Lucene index code and inlines the required Lucene
libraries. It can import the relevant SPI interfaces from {{oak-core}} and
export its functionality as OSGi services. Or a non-OSGi deployment like
{{oak-run}} can simply embed the combined {{oak-lucene}} jar and directly
instantiate the relevant classes.
> Embed lucene dependency into oak-jcr OSGI bundle
> ------------------------------------------------
>
> Key: OAK-438
> URL: https://issues.apache.org/jira/browse/OAK-438
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: jcr
> Reporter: Alex Parvulescu
> Attachments: OAK-438.patch
>
>
> Given the fact that lucene does not provide osgi headers OOTB, we have to
> embed the dependency into the oak-jcr bundle.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
