[Oak origin/trunk] Apache Jackrabbit Oak matrix - Build # 1253 - Failure

The Apache Jenkins build system has built Apache Jackrabbit Oak matrix (build #1253) Status: Failure Check console output at https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/1253/ to view the results. Changes: [tomekr] OAK-5035: Implement mini-benchmark for the

globbing: oak style vs sling style

Hi, As being discussed in [0] in OAK-5021 there are 2 different ways how globbing is currently defined in Oak vs in Sling. In Oak globbing is restricted to ** being 0-n path elements and * being 1 path element, while in Sling it is more generic in that * means 0-n characters excluding path

Re: globbing: oak style vs sling style

I just would like to add that this is not Sling's invention, but the pattern matching known to Java developers since more than ten years. First time i've seen it was in Ant: http://ant.apache.org/manual/dirtasks.html#patterns I think the usage of the "?" is very rare and potentially not needed

Re: segment-tar depending on oak-core

Hi all My preference is also with a higher degree of modularity. Compared to a monolithic application it is a trade-off that leads to both, higher complexity and higher flexibility. Provided we are willing to change and learn, I am sure we can easily manage the complexity. Numerous benefits of

Re: globbing: oak style vs sling style

I've created https://issues.apache.org/jira/browse/OAK-5039 to follow up Cheers, Stefan On 31/10/16 14:18, "Stefan Egli" wrote: >Hi, > >As being discussed in [0] in OAK-5021 there are 2 different ways how >globbing is currently defined in Oak vs in Sling. In Oak

Re: [REVIEW][API] Additions to JackrabbitEventFilter

(+oak-dev as it meanwhile has move to oak features alone) I've committed OAK-5013 which introduces the OakEventFilter extension and a number of such extensions (OAK-5019, OAK-5020, OAK-5021, OAK-5022, OAK-5023). While they should all in principle work I don't consider them as done yet as the