[jira] [Commented] (OAK-1426) Cleanup options in oak-run

["angela (JIRA)" <ji...@apache.org>]

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

angela commented on OAK-1426:
-----------------------------

at rev. 1576011 i committed the following changes:

1. OakRepositoryFixture + BenchMarkRunner 

- rename Oak-Default to Oak-H2 as this is no longer our default setup and adjusted the README accordingly
- added separate fixtures for in memory based on NodeStore and on MicroKernel. the default in memory setup is now on NodeStore.
  the naming is consistent with the one use for the different Mongo fixtures.

2. simplified the different run-modes defined in the Main class and justed the README (some newer modes were missing altogether). the setup now has the following modes:

- backup
- benchmark
- debug (used to be tarmk, also added a TODO as this should be available for other repositories)
- server 
- upgrade

3. JcrRemoting setup in the 'server' mode

- fixed the issue mentioned by alex above
- replaced 'JCRWebdavServerServlet' by 'JcrRemotingServlet' as the former is the outdated version that doesn't deal with JSON get and post requests.
- replace the name 'davex' by 'jcrremote' which is more accurate.

- 

> Cleanup options in oak-run
> --------------------------
>
>                 Key: OAK-1426
>                 URL: https://issues.apache.org/jira/browse/OAK-1426
>             Project: Jackrabbit Oak
>          Issue Type: Wish
>          Components: run
>            Reporter: angela
>            Priority: Minor
>             Fix For: 0.20
>
>
> i would like us to clean up the oak-run module such that it only contains parts that we are actively using and supporting.
> looking at the current options, i suspect the following being used/tested:
> - "benchmark"
> - "upgrade"
> - "backup"
> what else?



--
This message was sent by Atlassian JIRA
(v6.2#6252)