Details
-
Task
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
Description
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 | oak-operations | |
| DataStoreCheck | oak-operations | |
| Garbage | oak-operations | |
| tarmkdiff | oak-operations | |
| tarmkrecovery | oak-operations | |
| graph | oak-development | |
| history | oak-operations | |
| index | oak-operations | |
| persistentcache | oak-operations | |
| resetclusterid | oak-operations | |
| threaddump | oak-development | |
| tika | oak-operations |
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.
Attachments
Issue Links
- is related to
-
-
- Closed
-