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

The Apache Jenkins build system has built Apache Jackrabbit Oak matrix (build #938) Status: Still Failing Check console output at https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/938/ to view the results. Changes: [angela] OAK-4379 : Batch mode for SyncMBeanImpl [angela]

Re: [VOTE] Release Apache Jackrabbit Oak 1.5.3

hi julian that looks pretty similar to OAK-4382 they have in common that they sync (or should sync) group-membership with infinite nesting (in the test-setup the nesting in anyway just 2). but i can't reproduce neither issue on my machine;

Re: [VOTE] Release Apache Jackrabbit Oak 1.5.3

On 2016-06-06 17:04, Davide Giannella wrote: A candidate for the Jackrabbit Oak 1.5.3 release is available at: https://dist.apache.org/repos/dist/dev/jackrabbit/oak/1.5.3/ The release candidate is a zip archive of the sources in: ... I'm getting test failures in oak-auth-external:

Re: [VOTE] Release Apache Jackrabbit Oak 1.5.3

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

[VOTE] Release Apache Jackrabbit Oak 1.5.3

A candidate for the Jackrabbit Oak 1.5.3 release is available at: https://dist.apache.org/repos/dist/dev/jackrabbit/oak/1.5.3/ The release candidate is a zip archive of the sources in: https://svn.apache.org/repos/asf/jackrabbit/oak/tags/jackrabbit-oak-1.5.3/ The SHA1 checksum of the

Re: deploying oak-segment-tar to nexus

Hi Francesco, thanks for the clarification, it makes sense. Best regards, Tomek -- Tomek Rękawek | Adobe Research | www.adobe.com reka...@adobe.com > On 06 Jun 2016, at 15:23, Francesco Mari wrote: > > The maven-deploy-plugin is disabled for oak-segment-tar to

Re: Oak 1.5.3 release plan

On 02/06/2016 12:28, Robert Munteanu wrote: > > What's the current plan for releasing 1.5.3? > > I'm trying to take advantange of the recent enhancements to Oak/Jcr and > remove emebdding of oak-jar from Apache Sling, but can't work with > 1.5.2 due to OAK-4375 . > > Thanks, > > Robert > I had a

Re: deploying oak-segment-tar to nexus

The maven-deploy-plugin is disabled for oak-segment-tar to avoid that module from being released. We didn't agree on the release policy for that module. In particular, is not clear to us if oak-segment-tar should be released during the biweekly release process or if it should be released

deploying oak-segment-tar to nexus

Hello, I’ve noticed that the maven-deploy-plugin is disabled for the oak-segment-tar. As a result, the 1.5.2 release is not quite consistent (oak-jcr and oak-upgrade depend on the oak-segment-tar, which isn’t available in the remote repository). Should we re-enable the plugin before the 1.5.3