[
https://issues.apache.org/jira/browse/OAK-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chetan Mehrotra updated OAK-1896:
---------------------------------
Attachment: OAK-1896.patch
[patch|^OAK-1896.patch] which uses maven-assembly-plugin to create two run jars
* oak-run-xxx-oak.jar - Contains Oak related binaries including oak-lucene.
Does not include Jackrabbit core
* oak-run-xxx-jr2.jar - Contains Oak related binaries and Jackrabbit Core. Does
not include oak-lucene. This maps closely to current oak-run jar
*Changes done*
# Uses maven-assembly-plugin instead of maven-shade-plugin to create two jar
# Due to requirement to produce two jars the primary artifact is now simple
oak-run (which does not include dependencies). Instead 2 more jars are produced
and attached with classifier oak and jr2 respectively
# Eliminated quite a few dep which bring down the size from
#* ~38 MB to 29 MB - For oak
#* ~35 MB to 31 MB - For oak-jr2
# For using in IDE two profiles are created
## ide - Enable this to use oak-lucene related code
## jr2 - Enable this to use Jackrabbit related code
# Removed dependency on org.apache.jclouds.provider as currently its not being
used and was pulling in quite a few dependencies
*Change in compatibility*
If any component was using oak-run then it has to use oak-run-xxx-jr2
[~jukkaz] Can you have a look. I am primarily need this feature to add console
command to dump Lucene directory and for that I need to enable inclusion of
oak-lucene
[~rogoz] The change in jar name might affect you as you use it for running
benchmark
> 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)
