On 03/09/2015 09:31, Julian Sedding wrote: > Hi Tomek > > I believe that benchmarks in oak-run also use Jackrabbit 2 (via fixtures). > However, OAK-3342 proposes moving the benchmarks into their own module. > > Looking at this from a less technical perspective, I propose to split > oak-run into three modules: > > - oak-dev-tools (benchmarks, scalability, etc), size does not matter so > much, as devs probably build it themselves > - oak-upgrade (all things copying repositories between persistence > formats), contains JR2 > - oak-ops-tools (tools used for operating an Oak repo: inspecting, > checking, console, etc. may also contain NodeStore copy for convenience if > code duplication can be avoided), does NOT contain JR2 > > Naming is of course up for debate. Let's just discuss if a split along > these lines makes sense for now. > > WDYT? I'm more than happy to split oak-run. That's why I created the issue around benchmarks. It's the only clear area I could identify and know how it works.
I already filed a month ago a ticket around all the functionality for oak run: https://issues.apache.org/jira/browse/OAK-3134 Can we follow-up there the discussions around what modules we should create off oak-run? Davide
