On 10/02/2017 14:01, Thomas Mueller wrote: > Hi, > > What about moving benchmarks to a new module oak-benchmark? I'm not sure > if it's feasible, and not sure if it would reduce the size a lot. But it > is easy to understand, where oak-operations and oak-development is quite > fuzzy.
Reflecting over the original proposal we came in jira in 2015[0], I thought it would have been better to keep oak-run for the production operations (compactions, etc) while moving benchmarks and similar to oak-devel (or whatever other name we may fancy). (0) https://issues.apache.org/jira/browse/OAK-3134 The story behind this is that after an initial investigation a year ago we discovered that largest part of oak-run size, was taken by libraries which we actually use in a "development phase" like, but not limited to, benchmark[1]. (1) https://issues.apache.org/jira/browse/OAK-3766 By simply moving away such code, that doesn't need to be deployed into maven, we are going to cut considerably the size in oak-run. Still the pain point around backport remains. Davide
