[
https://issues.apache.org/jira/browse/OAK-3134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15870012#comment-15870012
]
Alex Parvulescu commented on OAK-3134:
--------------------------------------
bq. The terms "operations" and "development" sound quite fuzzy (to me).
I agree with the sentiment. It seems we're putting a lot of resources into
splitting the 2, and I'm not convinced about the end goal here. I definitely
want to have the _development_ deployed to maven central, if we end up
splitting. how else would I get feedback on it? how could one feature
transition from _development_ into _operations_ if it's not available for use?
If we need to split, I would bundle both into the same jar and simply output a
warning when using _development_ stuff along the lines of 'you are using dev
stuff, stuff might break, take special care'.
bq. I would prefer moving "benchmarks" (not listed above) to a new module
+1. if we simply move benchmarks to a jar that is not deployed, does that not
suffice for our bandwidth saving goals?
> 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 | | 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.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
