You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Amit Jain (JIRA)" <ji...@apache.org> on 2014/09/30 09:43:02 UTC

[jira] [Updated] (OAK-1896) Move JR2 specific logic from oak-run to separate module

     [ https://issues.apache.org/jira/browse/OAK-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Amit Jain updated OAK-1896:
---------------------------
    Fix Version/s:     (was: 1.1)
                   1.1.0

> 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.0
>
>         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
(v6.3.4#6332)