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

The Apache Jenkins build system has built Apache Jackrabbit Oak matrix (build #1205) Status: Still Failing Check console output at https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/1205/ to view the results. Changes: [frm] OAK-4883 - Register a BlobGCMBean on standby instances

Re: Possibility of making nt:resource unreferenceable

Hi, > >Currently I am under the impression that we have no knowledge of what >*might* break, with varying opinions on the matter. Maybe we should to >find out what *does* break. I don't think it's possible to easily find out. Customer code might expect the current behavior, and might silently

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

The Apache Jenkins build system has built Apache Jackrabbit Oak matrix (build #1204) Status: Still Failing Check console output at https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/1204/ to view the results. Changes: [amitj] OAK-4902: Blob GC completion time should be logged

[Oak origin/1.2] Apache Jackrabbit Oak matrix - Build # 1203 - Failure

The Apache Jenkins build system has built Apache Jackrabbit Oak matrix (build #1203) Status: Failure Check console output at https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/1203/ to view the results. Changes: [amitj] Oak 1.2.20 release notes [amitj] [maven-release-plugin]

Re: Possibility of making nt:resource unreferenceable

On Wed, Oct 12, 2016 at 11:24 AM, Bertrand Delacretaz wrote: > On Wed, Oct 12, 2016 at 11:18 AM, Julian Sedding wrote: >> ...As a remedy for implementations that rely on the current referencable >> nature, we could provide tooling that automatically

Re: [VOTE] Release Apache Jackrabbit Oak 1.5.12

On Tue, Oct 11, 2016 at 3:27 PM, Davide Giannella wrote: > Please vote on releasing this package as Apache Jackrabbit Oak 1.5.12. > The vote is open for the next 72 hours and passes if a majority of at > least three +1 Jackrabbit PMC votes are cast. > +1 Release this package

Re: Possibility of making nt:resource unreferenceable

On Wed, Oct 12, 2016 at 11:18 AM, Julian Sedding wrote: > ...As a remedy for implementations that rely on the current referencable > nature, we could provide tooling that automatically adds the > "mix:referencable" mixin to existing nt:resource nodes... Good idea, I suppose

Re: Possibility of making nt:resource unreferenceable

I'm with Julian R. on this (as I understand him). We should change the node-type nt:resource to match the JCR 2.0 spec and deal with the consequences. Currently I am under the impression that we have no knowledge of what *might* break, with varying opinions on the matter. Maybe we should to find

Re: Possibility of making nt:resource unreferenceable

The latest proposal was not about making nt:resource unreferenceable, but silently changing the resource type for a nt:resource child node of a nt:file node to Oak:Resource. I just found three other places in Sling where nt:file nodes are created by hand. So with any other mechanism we have to

Re: Possibility of making nt:resource unreferenceable

Hi, I agree with Julian, I think making nt:resource unreferenceable would (hardcoding some "magic" in Oak) would lead to hard-to-find bugs and problems. > So whatever solution we pick, there is a risk that existing code fails. Yes. But I think if we create a new nodetype, at least it would be

Re: [VOTE] Release Apache Jackrabbit Oak 1.2.20

[X] +1 Release this package as Apache Jackrabbit Oak 1.2.20

Re: [VOTE] Release Apache Jackrabbit Oak 1.2.20

On 2016-10-12 07:36, Amit Jain wrote: ... [X] +1 Release this package as Apache Jackrabbit Oak 1.2.20 Best regards, Julian