jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Francesco Mari (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-3134) Identify functionality offered by oak-run
Date Wed, 08 Feb 2017 09:57:42 GMT

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

Francesco Mari commented on OAK-3134:
-------------------------------------

+1 for every module marked with my name - even if I'm not the original developer of all that
stuff!

> Identify functionality offered by oak-run
> -----------------------------------------
>
>                 Key: OAK-3134
>                 URL: https://issues.apache.org/jira/browse/OAK-3134
>             Project: Jackrabbit Oak
>          Issue Type: Task
>          Components: run
>            Reporter: Davide Giannella
>            Assignee: Davide Giannella
>
> oak-run reached the size of 50MB+ and offers indeed various functionalities that could
be moved to their own module.
> This ticket is about to identify what oak-run currently offers and what/if could be split.
> ML thread: http://markmail.org/thread/w34bphrk57l7pkaz
> || Functionality || Package || Module ||
> | Backup | | oak-operations|
> | Check | | oak-operations|
> | Checkpoints | | oak-operations|
> | Compact | | oak-operations|
> | Debug | | oak-operations|
> | Explore | |oak-development |
> | Groovy console | org.apache.jackrabbit.oak.console, /oak-run/src/main/groovy/org/apache/jackrabbit/oak/console
| oak-operations|
> | Primary | | oak-development|
> | Recovery | | oak-operations|
> | Repair | | oak-operations|
> | Restore | | oak-operations|
> | Server | | oak-development|
> | Standby | | oak-development|
> | Upgrade | | oak-upgrade|
> | micro-benchmark | org.apache.jackrabbit.oak.benchmark |oak-development |
> | scalability benchmark | org.apache.jackrabbit.oak.scalability | oak-development|
> | DataStoreCacheUpgrade | | |
> | DataStoreCheck | | |
> | Garbage | | |
> | Graph | | |
> | Help | | |
> | History | | |
> | Index | | |
> | PersistentCache | | |
> | ResetClusterId | | |
> | TarMKDiff | | |
> | TarMKRecovery | | |
> | ThreadDump | | |
> | Tika | | |
> Modules left after the actions:
> **oak-development**
> Used to group and execute all the tools used during development.
> _deployed to maven:_ No.
> **oak-operations**
> Used to group and execute all the tools used normally in production environment for tasks
like maintenance & C.
> _deployed to maven:_ Yes.
> **oak-run**
> Will group what's left after the split.
> _deployed to maven:_ No.
> **oak-upgrade**
> Will group tools for upgrading/migrating from one repo/version to another
> _deployed to maven:_ yes.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message