[
https://issues.apache.org/jira/browse/OAK-3134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella updated OAK-3134:
----------------------------------
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 ||
| micro-benchmark | org.apache.jackrabbit.oak.benchmark |oak-development |
| scalability benchmark | org.apache.jackrabbit.oak.scalability |
oak-development|
| Groovy console | org.apache.jackrabbit.oak.console,
/oak-run/src/main/groovy/org/apache/jackrabbit/oak/console | oak-operations|
| Backup | | oak-operations|
| Restore | | oak-operations|
| Debug | | oak-operations|
| Check | | oak-operations|
| Compact | | oak-operations|
| Server | | oak-development|
| Upgrade | | oak-upgrade|
| Explore | |oak-development |
| Primary | | oak-development|
| Standby | | oak-development|
| Help | | |
| Checkpoints | | oak-operations|
| Recovery | | oak-operations|
| Repair | | oak-operations|
| 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.
was:
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 ||
| micro-benchmark | org.apache.jackrabbit.oak.benchmark |oak-development |
| scalability benchmark | org.apache.jackrabbit.oak.scalability |
oak-development|
| Groovy console | org.apache.jackrabbit.oak.console,
/oak-run/src/main/groovy/org/apache/jackrabbit/oak/console | oak-operations|
| Backup | | oak-operations|
| Restore | | oak-operations|
| Debug | | oak-operations|
| Check | | oak-operations|
| Compact | | oak-operations|
| Server | | oak-development|
| Upgrade | | oak-upgrade|
| Explore | |oak-development |
| Primary | | oak-development|
| Standby | | oak-development|
| Help | | |
| Checkpoints | | oak-operations|
| Recovery | | oak-operations|
| Repair | | oak-operations|
| Tika | | |
> Identify functionality offered by oak-run
> -----------------------------------------
>
> Key: OAK-3134
> URL: https://issues.apache.org/jira/browse/OAK-3134
> Project: Jackrabbit Oak
> Issue Type: Epic
> 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 ||
> | micro-benchmark | org.apache.jackrabbit.oak.benchmark |oak-development |
> | scalability benchmark | org.apache.jackrabbit.oak.scalability |
> oak-development|
> | Groovy console | org.apache.jackrabbit.oak.console,
> /oak-run/src/main/groovy/org/apache/jackrabbit/oak/console | oak-operations|
> | Backup | | oak-operations|
> | Restore | | oak-operations|
> | Debug | | oak-operations|
> | Check | | oak-operations|
> | Compact | | oak-operations|
> | Server | | oak-development|
> | Upgrade | | oak-upgrade|
> | Explore | |oak-development |
> | Primary | | oak-development|
> | Standby | | oak-development|
> | Help | | |
> | Checkpoints | | oak-operations|
> | Recovery | | oak-operations|
> | Repair | | oak-operations|
> | 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
