On 24/03/2017 16:24, Davide Giannella wrote:
> I've attached in the ticket the patch for review.
>
> https://issues.apache.org/jira/browse/OAK-3342
>
> I don't really know about backports though. The fact that in the past we
> split into separate commands will mean that if backporting anything from
I've attached in the ticket the patch for review.
https://issues.apache.org/jira/browse/OAK-3342
I don't really know about backports though. The fact that in the past we
split into separate commands will mean that if backporting anything from
oak-run the only pain points will be: Main and Modes.
On 22/03/2017 15:45, Angela Schreiber wrote:
> Just had a first look: there are some scripts inside oak-run that can be
> used to run benchmarks (which I actually do regularly). those are missing
> in your fork oak-benchmarks module. Please make sure you move them as
> well... i will also add this
Hi Davide
Just had a first look: there are some scripts inside oak-run that can be
used to run benchmarks (which I actually do regularly). those are missing
in your fork oak-benchmarks module. Please make sure you move them as
well... i will also add this to the issue.
Thanks
Angela
On 22/03/17
Hello Team,
as was discussed on OAK-3134[0], as part of [1] I'm going through the
effort of moving the benchmarks we have in oak-run into their own
module. This should allow us to then remove the dependencies from
oak-run that by the investigation making the size of the module big.
(0)
https://is
