BUILD FAILURE: Jackrabbit Oak - Build # 289 - Still Failing

2017-05-12 Thread Apache Jenkins Server
The Apache Jenkins build system has built Jackrabbit Oak (build #289) Status: Still Failing Check console output at https://builds.apache.org/job/Jackrabbit%20Oak/289/ to view the results. Changes: [alexparvulescu] OAK-3342 move benchmarks in oak-benchmark module - readding h2 dependency to ha

Re: Enforcing minimal test coverage

2017-05-12 Thread Matt Ryan
On Thu, May 11, 2017 at 6:03 AM, Angela Schreiber wrote: > hi julian > > no i didn't, because i don't think it makes sense to enforce a running > mongoDB for being able to build oak-core. nor does it make sense to me to > require a coverage that can only be reached with the derby-rdb profile > en

Re: Enforcing minimal test coverage

2017-05-12 Thread Matt Ryan
Hi, Speaking generally I think this is a good idea for Oak, so I am appreciative of the proposal. I assume we are talking about enforcement via build automation, meaning there would be a step in the build that would compute the coverage number and fail the build if the coverage number is not met.

Re: new name for the multiplexing node store

2017-05-12 Thread Matt Ryan
Likewise, the concept previously known as federated data store will now become CompositeDataStore. On Thu, May 11, 2017 at 7:27 AM, Tomek Rekawek wrote: > Hello, > > so, it seems we have the consensus. I’ll rename the implementation to > CompositeNodeStore and the module to oak-store-composite t

BUILD FAILURE: Jackrabbit Oak - Build # 288 - Failure

2017-05-12 Thread Apache Jenkins Server
The Apache Jenkins build system has built Jackrabbit Oak (build #288) Status: Failure Check console output at https://builds.apache.org/job/Jackrabbit%20Oak/288/ to view the results. Changes: [tomekr] OAK-6136: Extract the multiplexing implementation code into a separate bundle Renamed the bu