jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Dürig (JIRA) <j...@apache.org>
Subject [jira] [Commented] (OAK-1896) Move JR2 specific logic from oak-run to separate module
Date Wed, 02 Jul 2014 11:21:24 GMT

    [ https://issues.apache.org/jira/browse/OAK-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14049825#comment-14049825

Michael Dürig commented on OAK-1896:

I think a better way would be to modularise {{oak-run}} and run it in an OSGi container, which
should allow us to use all the required Lucene versions. See also http://markmail.org/message/nj24s2a7hy6xhgi4.This
would avoid the complexity leaking through (multiple artefacts with almost the same functionality,
maintaining and documenting this). 

> Move JR2 specific logic from oak-run to separate module
> -------------------------------------------------------
>                 Key: OAK-1896
>                 URL: https://issues.apache.org/jira/browse/OAK-1896
>             Project: Jackrabbit Oak
>          Issue Type: Task
>          Components: run
>    Affects Versions: 1.0
>            Reporter: Chetan Mehrotra
>            Assignee: Chetan Mehrotra
>             Fix For: 1.1
>         Attachments: OAK-1896.patch
> Currently oak-run module packages quite a few tools (benchmark, server, console, upgrade
etc). Some of these like benchmark and upgrade require JR2 binaries embeded within oak-run.
> This causes conflict with oak-lucene as it requires Lucene 4.x while JR2 requires Lucene
3.x. It would be simpler to move JR2 specific logic to a different module (oak-jr2?) and let
oak-run use all modules of oak
> [1] http://markmail.org/thread/ekyvuxxvdnbtsjkt

This message was sent by Atlassian JIRA

View raw message