[
https://issues.apache.org/jira/browse/OAK-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14062101#comment-14062101
]
Jukka Zitting commented on OAK-1896:
------------------------------------
The Lucene part is indeed troublesome, and the upgrade code currently does need
access to Jackrabbit internals. See
http://markmail.org/message/lgvbvw742zryhlmp and
http://markmail.org/message/mkzswwwde4zr454v for more background on those
issues.
I don't have a very good suggestion on how to best address this. For the
specific requirement of dumping the Lucene index files, we could actually skip
the Lucene dependency and instead directly copy the content from the index
subtree.
> 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
(v6.2#6252)
