[Oak origin/1.2] Apache Jackrabbit Oak matrix - Build # 851 - Still Failing

The Apache Jenkins build system has built Apache Jackrabbit Oak matrix (build #851) Status: Still Failing Check console output at https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/851/ to view the results. Changes: No changes Test results: 2 tests failed. FAILED:

[Oak origin/1.4] Apache Jackrabbit Oak matrix - Build # 850 - Still Failing

The Apache Jenkins build system has built Apache Jackrabbit Oak matrix (build #850) Status: Still Failing Check console output at https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/850/ to view the results. Changes: No changes Test results: 3 tests failed. FAILED:

Re: Cannot create JIRA issue for JCR project

I added Julian's account to the PMC role of the JCR project in Jira. Best, Jukka On Fri, Apr 22, 2016 at 2:24 PM Robert Munteanu wrote: > On Fri, 2016-04-22 at 15:27 +0200, Julian Sedding wrote: > > Hi all > > > > I can currently not log a JIRA issue for the JCR project.

Re: Cannot create JIRA issue for JCR project

On Fri, 2016-04-22 at 15:27 +0200, Julian Sedding wrote: > Hi all > > I can currently not log a JIRA issue for the JCR project. It is not > listed in the Create dialog's project dropdown. Other projects, e.g. > Jackrabbit Oak, Sling etc. are listed. > > Any ideas? Could it be related to the

Query related to Lucene property index

Hi All, We have a requirement wherein, we want to index all the properties for full text and then filter the results based on cq:tags. - compatVersion = 2 - type = "lucene" - async = "async" - jcr:primaryType = oak:QueryIndexDefinition + indexRules + nt:base + properties +

Cannot create JIRA issue for JCR project

Hi all I can currently not log a JIRA issue for the JCR project. It is not listed in the Create dialog's project dropdown. Other projects, e.g. Jackrabbit Oak, Sling etc. are listed. Any ideas? Could it be related to the recent infra changes on JIRA? Should I contact infra? Thanks Julian

Re: In search for a final name for oak-segment-next

As express offline, I would better choose a name that describes what the module does without leaking how the module works internally. My proposals are along the lines of "oak-local-store" and "oak-embedded-store". If having "segment" in the name is a major concern, I would opt for

In search for a final name for oak-segment-next

Hi, The new oak-segment-next module [1] is in place. Now we need to decide on a final name [2]. Please use this thread to express ideas, suggestions and concerns. If necessary I'll cast a vote on a couple of candidates later. My concerns are: - Keep "segment" in the name. As it is sill

Oak 1.4.2 release plan

Hello team, I'm planning to cut Oak 1.4.2 next Monday 25th April 2016. If there are any objections please let me know. Otherwise I will re-schedule any non-resolved issue for the next iteration. Thanks Davide

[Oak origin/trunk] Apache Jackrabbit Oak matrix - Build # 849 - Still Failing

The Apache Jenkins build system has built Apache Jackrabbit Oak matrix (build #849) Status: Still Failing Check console output at https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/849/ to view the results. Changes: [angela] OAK-3211 : Document External Identity Management

[Oak origin/1.4] Apache Jackrabbit Oak matrix - Build # 848 - Still Failing

The Apache Jenkins build system has built Apache Jackrabbit Oak matrix (build #848) Status: Still Failing Check console output at https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/848/ to view the results. Changes: [tomekr] OAK-4166: Fixed version-related properties for the